Apps for customers, staff and riders — one codebase, both app stores.
Most business apps are forms, lists, maps and notifications, and one codebase can serve both iOS and Android well. That halves the cost and means a feature reaches every user at the same time, instead of one platform falling behind.
For Prime Express we built three apps on one codebase: one for customers tracking a parcel, one for riders on the road, and one for the admin team. They share a backend, so a status change is visible everywhere at once.
We test on mid-range Android first, keep the download small, and make sure the app still works when the connection drops — which matters for anyone working in the field.
Cost is driven by the number of roles, not the number of screens. An app where everyone sees the same thing is straightforward. An app where a customer, a rider, a branch manager and an admin each need their own view is four products sharing a backend, and it should be scoped and priced that way from the start.
Publishing is its own piece of work, and it is where first-time app projects usually stall. Apple and Google both review submissions, both reject for reasons that are not always obvious, and both want privacy declarations, screenshots and store copy before they will look at the build. We handle that under your developer accounts and budget for a review cycle rather than assuming the first submission passes.
What’s included
- iOS and Android from a single codebase
- Separate apps for customers, staff or riders where the roles differ
- Offline handling for field work on a weak connection
- Push notifications, and SMS or WhatsApp where that reaches people better
- Publishing to the App Store and Google Play under your own accounts
- Updates and maintenance as the platforms change each year
How the work runs
- 1ScopingWe map every role — customer, staff, rider, admin — and the journeys each repeats daily.
- 2DesignScreens designed for a phone in one hand, reviewed before development starts.
- 3BuildOne codebase for iOS and Android, with test builds you can install as we go.
- 4ReleaseStore listings, review submission, then updates as the platforms change each year.
What you get
- iOS and Android apps from one codebase
- Store listings published under your own accounts
- The backend and APIs the apps run on
- Test builds throughout, not just at the end
- Source code and release documentation
Questions
- Do I need separate apps for iOS and Android?
- No. One codebase produces both, which halves the cost and means a feature reaches every user at the same time rather than one platform falling behind.
- Do I need an app at all?
- Often not. If customers would use it occasionally, a fast mobile website reaches more of them with nothing to install. We will say so if that is the better answer.
- Who owns the App Store and Play accounts?
- You do. We publish under your developer accounts, so the apps stay yours if you ever change developer.
- Can one app serve customers and staff?
- It is usually better as separate apps sharing one backend — a customer app and a rider or admin app — because the roles need very different screens.
- What does a mobile app cost in Nepal?
- Enough that it is worth checking whether a fast mobile website would do the job first. Where an app is genuinely the right answer, the cost follows the number of distinct roles it serves, so we scope those before quoting.
- How do updates work after launch?
- Both platforms change every year, and an app nobody maintains eventually stops installing. A maintenance arrangement covers the platform changes, the security updates and the small changes real use reveals.
Our work in this area
Related reading