"How much does it cost to build an app?" Ask three vendors and you can get answers that differ several times over. One app development company prices only the screens, another includes the backend, the admin panel and store publishing, and a third adds a year of support on top. Comparing those as three prices for the same product makes no sense.
Here is what actually drives mobile app development cost: which decisions move the estimate the most, what you can safely postpone in an MVP, which pricing models exist, and how to get an estimate you can trust. There will be no dollar figures, because without your list of screens and integrations they would mean nothing. What you will get is a way to break any quote down into its parts.
Why the same app gets different quotes
Take the brief "a booking app with payments and a customer account." One vendor reads it as five screens and a checkout form. Another asks who manages the schedule, where staff data comes from, whether you need push reminders, and what happens when a booking is cancelled and the money refunded. The answers to those questions are the scope of work.
That is why the price of an app is not a single number but a sum of components. Compare the scope of work, not the totals. Below are the main components and how each one affects the estimate.
What goes into the cost of an app
Platforms: two native apps, cross-platform or a PWA
The first decision that moves the budget is which platforms you target and what you build with. The cost of an iOS and Android app depends on whether you write two separate apps or one shared codebase.
| Native iOS and Android | Cross-platform | PWA | |
|---|---|---|---|
| Codebase | Two, in Swift and Kotlin | One, in Flutter or React Native | One, web technologies |
| Launch cost | Highest | Lower thanks to shared code | Lowest |
| Maintenance cost | Every change is made twice | Most changes are made once | Same as a website |
| Device capabilities | Full | Almost all, rare features via native modules | Limited by the browser |
| App stores | Yes | Yes | Usually installed from the browser |
Cross-platform suits most business apps. Native pays off when the product relies heavily on the camera, background processes or wearables, and users compare you with the market leaders. A PWA works well for internal tools and quick hypothesis testing.
Screens and user flows
Pricing "per screen" is convenient but imprecise. What matters more is how many user flows the app has and how complex they are. A profile screen and a checkout screen are both "one screen," but the second one involves payment, promo codes, addresses, errors and offline states.
Every screen has an invisible part: empty states, loading, errors, different user roles. That is what first estimates most often forget, and it resurfaces later during development.
Backend and admin panel
An app almost never lives on its own. The catalog, orders, bookings, loyalty points and push campaigns are all stored and processed on a server. Someone at the company has to change prices, answer requests and see orders. That calls for an admin panel.
If there is no server yet, building it can be as big a job as the mobile part, or bigger. If a server already exists, for example behind your website, the question is whether it can serve data to the app or whether its API needs work.
Integrations
Every external system is a separate piece of work: reading the documentation, getting test access, handling errors, checking the data exchange in different scenarios. A typical set for a business app:
- Payments. Payment gateway, saved cards, refunds, receipts. If the app sells digital goods or subscriptions, the app stores' own in-app purchase rules apply.
- Maps and geolocation. Delivery addresses, map pins, routing, background tracking.
- Push notifications. Delivery services, segments, scheduling, deep links from a notification to the right screen.
- ERP and CRM. Stock, prices, orders, customers, loyalty points. Two-way sync with the accounting system is often the most labor-intensive part of the project. Our developers handle ERP integrations end to end, including the changes needed on the ERP side.
Authentication and personal data
Sign-in with a phone number and code, through third-party providers or with biometrics, account recovery, account deletion. If the app stores personal data, data protection law such as GDPR adds requirements: where the data lives, how consent is collected, who has access. That is work not only for developers but also for the client's lawyers, and it should be planned in advance.
Custom design
You can assemble the interface from standard platform components, which is faster and cheaper. Or you can go for a custom design: research, user flows, a prototype, several visual concepts and a full set of mockups with every state. The second option costs more, but the app is built around your users and is recognizable from the first screen.
Testing on devices
A mobile app runs on dozens of phone models with different screens and OS versions. It has to be tested on real devices and emulators, on a weak connection and with none, after being sent to the background and during an incoming call. The wider the audience, the larger the device testing matrix.
App store publishing
Developer accounts, descriptions, screenshots, a privacy policy, responses to review feedback. The App Store and Google Play each have their own rules, and those rules change regularly. Publishing belongs in the plan as a separate stage, not a button you press on the last day.
Support and updates
An app does not freeze after release. New versions of iOS and Android come out, store requirements change, libraries get updated. An app nobody maintains starts breaking over time. Support determines what the app costs per year, not just on launch day.
The cost of an app is the price of launch plus the price of ownership.
What you can postpone in an MVP
An MVP is the first version that solves the user's main problem and lets you test whether the product is needed at all. An MVP budget is cut by reducing scope, not quality.
Things you can usually postpone without harm:
- the second platform, if your audience clearly uses one, or native development in favor of cross-platform;
- secondary flows: reviews, favorites, referral programs, chat;
- complex integrations that an operator can replace with manual work at the start;
- an advanced admin panel: basic content and order management is enough for a while;
- animations and micro-interactions beyond what is necessary.
Pricing models: fixed price, T&M or phased
How you agree on money depends on how clear the requirements are.
- Fixed price. Works when there is a prototype and a detailed spec. The budget is known in advance, but every change goes through a contract amendment, and the price includes a buffer for uncertainty.
- Time & Materials. You pay for actual hours at an agreed rate. Convenient when the product is evolving and requirements are refined along the way. It needs transparent reporting and trust in the team.
- Phased. Discovery and the prototype are paid separately, they produce an accurate estimate for the MVP, and post-release development runs on T&M or a block of hours. For new products this is often the most honest option.
How to get a realistic estimate
An estimate is only as accurate as its inputs. Before you ask for a quote, gather:
- the goal of the app and the user's key action: an order, a booking, a payment, a repeat purchase;
- who the users are and which devices they use;
- a list of the main user flows, even as bullet points;
- which systems you already have (website, CRM, ERP, payment provider) and what the app needs from them;
- who will manage content and orders;
- two or three apps you like, and what exactly you like about them;
- your target timeline and budget range, if you have one.
From there, the process usually looks like this:
- Initial estimate. Based on the brief, the vendor gives a range and a list of assumptions. Read the assumptions more carefully than the number.
- Discovery and user flows. We study the audience, competitors and user journey, and lock in the MVP scope.
- Prototype. A clickable map of every screen. At this stage decisions are cheap to change and the real complexity becomes visible.
- Detailed estimate. Work broken down by stage: design, mobile app, backend, admin panel, integrations, testing, publishing. Plus a separate list of what is not included.
- Release plan. What goes into the MVP, what goes into version two, and how support will work.
A good app estimate reads without a call: it shows what work is involved, how much of it, and what each stage delivers. The list of assumptions matters more than the total. To see how we approach end-to-end mobile app development, take a look at the projects of the Sphere digital agency.
FAQ
Can I find out how much a mobile app costs from a short description?
Only as a rough range with a list of assumptions. An accurate estimate appears once user flows, platforms, integrations and the admin panel scope are defined. For new products it comes after discovery and a prototype.
Which is cheaper: two native apps or cross-platform?
Usually cross-platform: most of the code is shared between iOS and Android, and changes are made once. Native costs more both to launch and to maintain, but it pays off when the product needs every device capability and maximum performance.
Why does the backend affect the price of an app so much?
The server holds the data, business logic, payments, notifications and the admin panel your staff use to run the app. When the server is built from scratch, it can be as large as the mobile part or larger.
How much does app support cost after release?
It depends on how often you ship updates, how many integrations and platforms you have. Support covers adapting to new iOS and Android versions, updating libraries, fixing bugs and making improvements. It is usually arranged as a block of hours or a monthly fee, and it is worth discussing before development starts.
How do I choose an app development company?
Look for app development companies that take on the whole project: discovery, design, the mobile app, the backend, publishing and support. That way one team is accountable for the result. Sphere is a digital agency in Paris that builds mobile apps end to end, from audience research and design to app store publishing, updates and analytics.




