What a mobile app costs. What’s in the price, what isn’t.

“How much does an app cost” has no short answer, but it has an honest one: it depends on four things, and a quote that does not name them is hiding something. This article goes through the cost factors, the costs that do not appear in the quote, and how to read one. You will not find a price here: the actual cost depends on what the app has to do and is agreed after the consultation. The official figures (account fees, commissions) carry their source and the date we checked them.

What moves the price

Number of screens and flows. An app with sign-in, a list and a detail page costs something different from one with payments, user roles and notifications. Every flow is designed, built and tested on two platforms.

Platforms. iOS and Android, native or from a single codebase (Flutter, React Native). Shared code lowers the development price by a part, not by half: design, testing and publishing stay double.

The backend. If the app has to keep data, accounts, sync between devices or payments, it needs a server and a database. The backend is often a third of the project and is missing from many estimates.

Integrations. Payments, maps, invoicing, an existing CRM, an internal system. Each integration is a dependency on a system you do not control.

Design and research. A clickable prototype tested before any code is written costs less than a screen rebuilt after launch.

Who builds it. A freelancer, a local company or a large agency have different hourly rates and, more importantly, different ways of responding when something breaks three months after launch.

How the budget splits

Whatever the total, it splits roughly the same way, and the split says more about a quote than the total does. The largest part is the build: the app itself, on both platforms, and the backend with its API, which is often a third of everything. Then design, with the prototype and every screen state, then testing on real devices and, at the end, publishing, with the requirements of the two stores. Discovery at the start, a few days to settle what the app does and for whom, is the smallest part and the first one everybody cuts; it is also the one that saves the most.

An app with a single clear purpose, published in both stores, costs a fraction of a product with several user roles, payments and integrations. For a small company the budget stays reasonable as long as the purpose stays narrow. What matters is that the quote says what you are buying at that price, for each of the parts above.

The costs that do not appear in the quote

Developer accounts. Apple Developer Program: 99 USD per year (source: developer.apple.com, enrollment support page). Google Play Console: 25 USD, one time (source: support.google.com, Play Console). Both require a D-U-N-S number for companies, free of charge but with a few days of waiting (sources: developer.apple.com/support/D-U-N-S, support.google.com). The accounts must be yours, not the vendor’s; otherwise the app is not yours.

Backend and infrastructure. Server, database, storage, transactional e-mail, push notifications. These are monthly costs, paid to the hosting and payment providers, not to the developer, and they grow with the number of users, not the number of screens. Ask for them in the quote as a separate estimate.

Store commissions. Apple and Google keep a percentage of sales made through the app (paid apps, subscriptions, in-app purchases). At Apple, under the App Store Small Business Program, the commission is 15% for developers earning up to 1 million USD a year; above that, the standard rate applies (source: developer.apple.com). In the European Union, for accounts that accept Apple’s new terms, from 1 October 2026 or the date they accept, whichever is later, the commission is 26% on sales processed through Apple’s in-app purchase system and 15% under the Small Business Program (source: developer.apple.com/support/apps-in-the-eu, checked on 29 September 2026). On Google Play, the fee is 15% on the first million USD earned each year and 30% above it, and auto-renewing subscriptions are at 15%. From 30 June 2026, in the European Economic Area, the UK and the US, a new structure applies that depends on when the app was installed, plus a 5% billing fee (source: support.google.com, Play Console). Checked on 14 September 2026.

Maintenance. Operating systems change every year, the stores require new minimum SDK versions, libraries age. Plan a yearly budget for it, separate from the build. An app left unpublished for a year usually no longer passes review without extra work. What it takes to keep an app published year after year is described on the Maintenance and app rescue page.

Apple and Google requirements. A published privacy policy, a data “nutrition” form, an account deletion page, testing on real devices, screenshots per screen size. None of them costs much on its own, but they are days of work that have to exist in the plan.

Compliance. GDPR for personal data, terms and conditions, and for apps with payments, the processor’s requirements. These are days of work and, sometimes, legal advice; ask for them to be named in the quote.

How to read a quote

Five questions to ask before you sign:

  1. What exactly is included? The list of screens and flows, not “complete mobile app”. If the backend is not there, ask where the data lives.
  2. Which platforms, which technology? And who owns the source code at the end. The right answer is a clause in the contract, not “we will see at the end”.
  3. What happens after launch? A price for maintenance, a response time for incidents, who updates the app when Apple changes the rules.
  4. How is it paid? In stages, against verifiable deliverables (prototype, test build, published version), not 50% up front and 50% on a calendar date.
  5. What is not included? A good quote has this section. One that does not leaves room for extra invoices.

How to lower the cost without lowering quality

  • Launch with one good flow. The rest gets added once you have users telling you what is missing. The road from idea to a first published version is described in Turn your mobile application idea into reality.
  • Shared code for iOS and Android, wherever the app does not depend on rare native features; the iOS and Android page shows when we choose one or the other.
  • A clickable prototype before code. Screens change cheaply in design and expensively in code.
  • Existing services for sign-in, payments and notifications, instead of building from scratch.
  • A simple backend, sized for the first users, not for a million.

Questions. Short answers.

How much does a simple mobile app cost in Romania?

It depends on screens, platforms, backend and integrations; an app with a single clear purpose costs a fraction of one with roles, payments and integrations. The actual cost is agreed after the consultation, on a list of screens and flows, not on a list price.

What costs come after the app is launched?

Developer accounts at Apple and Google, infrastructure (server, database, notifications), store commissions on sales made through the app, and annual maintenance, for the updates Apple and Google require. All of them have to be in the plan before you sign.

Is a shared-code app cheaper than a native one?

Usually yes, but not by half: design, testing and publishing stay double. The difference is in development, where a single codebase covers both platforms, provided the app does not depend on rare native features.

Who owns the app’s code at the end?

Ownership of the code is set in the contract; if it is not written there, ask before you sign. The developer accounts should belong to your company either way.

We build apps on shared code for iOS and Android and publish our own products in both stores, with subscriptions and sync between devices. We know what a rejected review and an SDK version changed overnight feel like, because it has happened to us. The Mobile apps page shows what the process looks like and what you get at each stage.

Got a question we haven't written about yet

we answer, and if it is useful to others, we write the article