A phone is where most people in Nepal meet your software, and an app is not a website in a smaller window. It is offline for part of the day, it is opened for thirty seconds at a time, and it has to survive a store review.
What we build
- One codebase, both stores — iOS and Android from the same source, so a fix ships to both and not to whichever we got to first
- Accounts and sync — data that is there in flight mode and settles correctly when the signal comes back, by a rule rather than by luck
- Notifications and deep links — the ones people keep, not the ones they disable in week one
- The server behind it — an app is a client; something has to be the source of truth, and you should be able to run it from a desk
What we will tell you first
Most first apps do not need to be apps. If a fast web page would reach more people for less, we will say so — the store review, the two release channels and the update everyone has to accept are real costs and they never go away.
Where an app is the right answer it is usually for one of three reasons: it needs the camera, the location or the hardware; it has to work with no signal; or people open it every day and a browser tab is friction. Any of those, and we are the right call.
Scoped in writing first
Every engagement starts with a written scope: what gets built, what it costs, and when it lands.