Skip to content
Since98
Insights · Build

How much does it cost to hire a mobile app developer: what drives the price and what comes after release

Ask five developers what an app costs and you get five different numbers, because each one prices a different app in their head. The price follows the scope: how many screens and user roles, which platforms, which systems the app talks to, and who runs it after release. This article walks through those decisions so you can ask for quotes that can be compared.

02 — Short answers

Short answer

What decides the cost of hiring a mobile app developer?

Short answer
The cost follows the scope of the first version: the number of screens and user roles, iOS, Android or both, integrations with your systems, an admin panel, and support after release. The seniority of the team changes how fast that scope is built and how many problems surface later.
How we do it
We quote a fixed price for the first version after a scoping session where we list screens, roles and integrations with you. That list is what makes two quotes comparable.
Limits
We do not publish a single starting price for apps, because two apps with the same idea can differ several times in scope. Store fees, servers and third-party services are paid on top of development.

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
DecisionSmaller scopeLarger scope
PlatformsOne platform, or one cross-platform codebaseSeparate native apps for iOS and Android
Screens and flowsA few core screens for one main taskMany flows, settings, onboarding, edge cases
User rolesOne type of userCustomers, staff, managers with different rights
IntegrationsNone, or a simple exportCRM, accounting, payments, Zalo OA, booking or ERP via API
Admin sideContent edited in a spreadsheet or existing toolA custom admin panel with reports
LanguagesOne languageVietnamese and English with switchable content
Offline and real timeOnline onlyOffline 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.

03 — FAQ

Questions readers ask

Can you give a price before we have a full specification?

We can give a range after a short call, and a fixed price after a scoping session. A full specification is not required; a clear list of screens, roles and integrations is.

Is a cross-platform app cheaper than two native apps?

Often, because one codebase serves both stores. It depends on how much the app uses device features; we check that during scoping.

Who pays the App Store and Google Play fees?

The app owner, from their own developer accounts. We recommend publishing under your company's accounts so you keep the app if you change teams.

Do we need an app at all?

Not always. If customers already talk to you in Zalo and the task is simple, a Zalo Mini App or a mobile website can be cheaper to build and easier to reach.

04 — Sources

Sources and notes

  1. 01Our quoting method for appsFixed price for the first version after scoping screens, roles and integrations; we do not publish a starting price for apps.
  2. 02Apple Developer ProgramMembership and publishing terms for the App Store; check current fees there
  3. 03Google Play ConsoleDeveloper account and publishing terms for Google Play; check current fees there
05 — Author

Who wrote this

Dmitry KaplanEngineering · Mobile · In software since 2008

One of the two founders of Since98. We write about what we set up for clients: what works, what it costs and where the limits are.

About the founders
06 — Articles

Read next

  • Build · 4 min read

    Zalo Mini App vs mobile app

    When a Mini App inside Zalo is enough, when you need a native iOS and Android app, and how to decide.

  • Build · 3 min read

    Website maintenance cost

    What a website maintenance fee covers, what makes it higher, and how to compare quotes in Vietnam.

08

Next step

Describe the situation in a few lines. One of the founders replies and says whether we can help and what the first step would be.

Discuss your project
Or write in a messenger: