Mobile app development,
both stores from one build.

Roughly half the cost of building each platform natively, because one team writes one app and ships it to both stores on one release cycle. It is not a free lunch: anything touching the camera, background location, push permissions or a store review still gets platform-specific work, and we scope that separately rather than pretending Flutter removes it.

Where the job needs it, yes. On the field-operations build, visits, fuel volumes and distances are written to the device the moment they happen and sync when the network returns, so an agent in a dead zone never loses an entry. Offline-first is a design decision made at the start; it is expensive to retrofit and we will tell you at scoping whether you need it.

No, and we will not invent them. The portfolio documents what was built and shipped — eight apps in production, 140+ screens, six sectors between 2022 and 2026 — and it contains no adoption, revenue, hours-saved or time-reduced figures at all. Those are scope figures and we label them as scope everywhere they appear. We are asking those clients for outcome data and will publish it when we have it in writing.

Four of the eight carry a public Google Play listing. The rest are enterprise deployments distributed inside an organisation. We state only whether a public store listing exists, because that is the fact anyone can check — we do not describe distribution arrangements we cannot evidence.

Partly. One is a national telecom operator, and we do not publish their name without their written permission even though our development partner's own portfolio names them. Another client is not named anywhere in our source material, so we will not guess. Where a name is cleared, we use it.

You do, outright. The repository is in your own accounts from the first commit, along with the signing keys and the store listings. There is no licence to renew and nothing stops working if you stop paying us.

No. The layout mirrors — navigation, back gestures, list order, form alignment and number formatting — rather than the strings being swapped inside a left-to-right shell. Arabic is set up in the first week of the build, because retrofitting it means revisiting every screen.

Send the idea and who uses it. A thirty-minute call is usually enough to say whether this needs a native app at all — for a lot of internal tools, a mobile web app is the honest answer and we will say so.