Why app quotes differ so much
An app idea in one sentence, such as “customers book and pay in the app”, can mean a few screens or a full product with accounts, payments, notifications, an admin panel and links to your accounting software.
When you send the same sentence to several teams, each fills the gaps with its own assumptions. One quote is low because it leaves out the admin panel; another is high because it includes things you never asked for. The fix is to describe the scope before comparing prices.
What drives the cost
These are the decisions that move the price, and you make them.
Scope decisions and their effect on cost| Decision | Smaller scope | Larger scope |
|---|
| Platforms | One platform, or one cross-platform codebase | Separate native apps for iOS and Android |
|---|
| Screens and flows | A few core screens for one main task | Many flows, settings, onboarding, edge cases |
|---|
| User roles | One type of user | Customers, staff, managers with different rights |
|---|
| Integrations | None, or a simple export | CRM, accounting, payments, Zalo OA, booking or ERP via API |
|---|
| Admin side | Content edited in a spreadsheet or existing tool | A custom admin panel with reports |
|---|
| Languages | One language | Vietnamese and English with switchable content |
|---|
| Offline and real time | Online only | Offline mode, live updates, maps and tracking |
|---|
Cross-platform frameworks often reduce cost when the app is mostly forms, lists and content. Apps that rely on device features may still need native work.
Fixed price or time and materials
A fixed price works when the first version can be described as a list of screens, roles and integrations. You know the cost in advance; changes outside the list are quoted separately.
Time and materials means you pay for the hours spent. It suits work where the scope will change every few weeks, such as an app you improve after watching how customers use it. It needs regular reviews of what was done, or the budget drifts.
A common middle path: a fixed price for the first version, then a monthly budget or hourly work for changes after release.
- Fixed price: predictable budget, needs a clear scope, changes are quoted one by one
- Time and materials: flexible, needs your time to set priorities and check progress
- Monthly retainer after release: a set amount of work each month for fixes and small features
Freelancer, agency or in-house developer
The same app costs differently depending on who builds it, and the difference is not only the rate.
A freelancer can be the cheapest option for a small app, but the project depends on one person's availability. An agency adds project management and more people, which costs more and helps when the app has several parts. An in-house developer makes sense once the app is a long-term product with constant changes; until then one person rarely covers design, iOS, Android and the server alone.
We are a studio of 2 senior engineers: you talk to the people who write the code, without account managers in between.
Costs that come after release
The development quote covers building the app. Running it is a separate line that is easy to leave out of the budget.
- Developer accounts in the App Store and Google Play, paid by the app owner to Apple and Google
- Servers, database and file storage for the app's backend
- Third-party services billed per use: maps, SMS or ZNS messages, push notifications, payment gateways
- Updates when Apple and Google release new OS versions or change store rules
- Bug fixes and small changes after customers start using the app
Store fees and rules change. Check the current terms on the Apple and Google developer pages before you budget; we do not quote them here.
How to get quotes you can compare
Send every team the same short brief. One page is enough if it answers the questions below.
- Who uses the app, and what is the one main task they do in it?
- Which screens do you expect, roughly, and which user roles?
- Which of your systems must the app read from or write to?
- iOS, Android or both? Is a Zalo Mini App or a mobile website an acceptable start?
- Who edits content and prices: your staff in an admin panel, or the developer?
- Who will publish the app, and under whose developer accounts?
How we price an app
We give a fixed price for the first version after a scoping session on screens, roles and integrations; the process is on our mobile app development service page. If a Zalo Mini App or a web version would do the job, we say so first.