App Development Cost: What Drives It and How to Get a Fixed Quote
What really drives mobile app cost: scope tiers and timelines for an MVP, a booking app and a marketplace, one codebase versus native, hidden costs, maintenance, comparing quotes and getting a fixed price.
This guide explains what really drives mobile app development cost in 2026, and how to get a fixed quote you can rely on. If you already know what you want to build, the React Native app development page shows our scope tiers and what is included.
How much does it cost to develop an app?
It is hard to give a single number, because the cost depends far more on what happens behind the screens than on how many screens there are. Who signs in? Where does the data live? How does money move? Which other systems does the app talk to? Each answer adds a known amount of work, and the price is the sum of that work.
That is why we do not quote from a price list. After a short call we write down the features, screens and timeline together with you, and send a price for that written scope. It covers both iOS and Android from one codebase, including design, development, testing and store submission, and it stays the same during the project.
Scope tiers and timelines
A simple app or MVP
6-8 weeks. One core flow, user accounts and notifications. Think of a loyalty card app, an internal field app for staff, or the first version of a startup idea built to test one assumption with real users.
An MVP is not a prototype. It is a live app in the stores that stores data and lets people sign up; it just does one thing instead of ten.
A booking app
Usually 8-12 weeks. A booking app looks simple on screen: pick a service, pick a time, confirm. Behind it sit availability rules, cancellations, reminders, often payments, and a web panel where the business manages its calendar. That admin side is frequently as much work as the app itself.
A very narrow booking app, with no payments and a simple admin view, can fit in the MVP tier. Most real booking products end up in the mid-size tier.
A marketplace
12+ weeks. A marketplace is two products in one: a side for customers and a side for providers, plus an admin panel to run the whole thing. It usually needs messaging between the two sides, split payments, ratings, location and plenty of notifications. That is why marketplaces sit in our complex tier.
What drives the cost
Every app starts from a base: design, a handful of screens, both platforms, testing and store submission. On top of that, these are the features that add the most work:
- User accounts and profiles: sign-up, sign-in, password reset, profile editing and account deletion.
- Push notifications: setup on both platforms, plus the logic for who gets which message and when.
- Payments or subscriptions: payment provider or in-app purchase setup, receipts, refunds and failed-payment handling.
- Web admin panel: a separate web interface where your team manages content, users or orders.
- Maps and location: map views, search by area, distance calculations and location permissions.
- Messaging / real time: chat or live tracking, which needs a real-time back end and careful testing.
- Connecting to an existing system (ERP, API): depends heavily on the quality of the other system's documentation.
- Offline mode: storing data on the device and syncing it safely when the connection returns.
- Multiple languages: translated interface texts, store listings and content in each language.
Two apps that look the same can differ a lot in cost. A restaurant app that shows a menu and one that takes the order, sends it to the kitchen, tracks the courier on a map and takes payment look alike on a phone. The work behind them is not.
One codebase or two native apps?
Building separate native apps for iOS and Android means two codebases, two test cycles and two maintenance tracks. With React Native, most of the app ships to both platforms from one codebase: design, business logic and tests are done once, and every later update ships to both platforms together.
That is the main reason our quotes always include both platforms. Some apps do need native development: games and heavy 3D, advanced augmented reality, low-level hardware access. Those are the exception. For booking apps, marketplaces, membership apps, internal tools and most startup products, one codebase is the sensible choice.
We built our own app Zamgo, fuel price alerts for Turkey, this way with React Native and Expo; it is live on the App Store and Google Play. We also rewrote Invite Me, a travel meetup app on the App Store since 2016, in React Native and Expo for its version 8, with realtime chat, Apple and Google sign-in and in-app subscriptions on both platforms.
Hidden costs to plan for
These are easy to overlook when planning a budget, and most of them recur.
- Store developer accounts: Apple charges a yearly developer fee and Google a one-off registration fee. Both accounts should be opened in your name.
- Servers and database: small at launch, growing with the number of users and the amount of data.
- Third-party services: SMS verification, email delivery, maps, push notifications, crash reporting. Most have free tiers and start charging as you grow.
- Store commission: Apple and Google take a commission on digital content and subscriptions sold in the app. Physical goods and services are paid through a normal payment provider instead.
- Privacy work: privacy policies, consent flows and account deletion, which both stores now require. Ask whether a quote includes it.
Why apps need regular maintenance
A website can often run untouched for a long time; a mobile app needs more regular attention. Apple and Google introduce new version requirements every year. Apps that are not updated can gradually become invisible on new devices.
So it helps to plan for maintenance as a recurring yearly cost rather than a one-off. It covers OS and store-policy updates, library upgrades, crash monitoring and bug fixes. New features are separate; if you plan to keep building, an ongoing monthly retainer, for at least 3 months, keeps a steady pace. It is worth getting the maintenance scope in writing together with the project quote.
An app budget is easier to judge when you look at its cost over two or three years, not only the first invoice.
How long it takes
Time and cost move together. An MVP takes 6-8 weeks, a mid-size app 8-12 weeks, and complex projects 12+ weeks. Store review comes on top of that. The most common cause of delay is not the code but decisions: content that is not ready, or scope that changes once development has started. A written scope agreed before work begins, and a working preview every week, keep both the timeline and the budget where they were planned.
What app developers cost: questions to ask when comparing quotes
It's normal for quotes to differ; often each company is pricing a slightly different scope. Comparing them against the same written scope helps, and these questions help you see which one fits you:
- Will the full source code be handed over to me?
- Whose name are the App Store and Google Play accounts in?
- Is the design made specifically for this app?
- Is the price fixed, or will it grow with hours spent?
- How often will I see working software during the project?
- Is store submission included, and who fixes a rejection?
- Who maintains the app after launch, and at what cost?
Clear, written answers to these questions make quotes much easier to compare.
How we arrive at a fixed price
- First call: who the app is for, the core flow and what it needs to connect to.
- Written scope: features, screens, platforms and what is explicitly left for later.
- Quote: one price and a timeline for that scope, agreed before work starts so you can plan your budget.
- Changes: a new idea mid-project either swaps with something in scope or is quoted separately for the next version.
Ways to lower the cost
The healthiest way to lower the budget is to build only what is truly needed in the first version.
- Starting with an MVP: the one flow that proves the idea comes first, and features are added based on how people actually use it.
- A simple admin side at first: early on, a ready-made content tool or even a spreadsheet can do the job of a custom panel.
- One codebase: iOS and Android ship together.
- Scope agreed in writing: scope that keeps changing during development tends to raise cost the most.
- Checking whether you need an app at all: if people will use the product once a month at a desk, a good web app may cost less and suit them better.
Next steps
For our scope tiers, timelines and what every project includes, see React Native app development. If you would like a price for your own feature list, you can write to us; we reply within 1 business day and send a written proposal after a short call.