Every founder asks the same first question, and every honest agency gives the same unsatisfying answer: it depends. This guide explains what it depends on, so you can estimate your own app before you talk to anyone, and so a quote makes sense when you get one.
Key takeaways
- The price of an app is set by scope, platforms, backend, integrations, design, compliance and who builds it, in roughly that order.
- A mobile app is usually two products: the app and the backend behind it. Forgetting the backend is the most common reason estimates are wrong.
- The cheapest way to reduce cost is to cut the first version, not the hourly rate.
- Running the app after launch costs money too: hosting, app store fees, updates and support.
Why there is no single number
Asking how much an app costs is like asking how much a building costs. A garden shed and a hospital are both buildings. An app that shows a menu and takes a booking shares almost nothing with an app that processes payments, syncs with a warehouse and works offline. Anyone who gives you a price before asking what the app does is guessing, or selling a template.
What you can do is understand the factors, place your own idea on each one, and arrive at a range. That is what the rest of this guide is for.
The seven factors that set the price
1. Scope: how many things the app does
Count the screens and the actions on each. Sign-up, a list, a detail view, a form and a profile is a small app. Add chat, payments, maps, notifications, search, roles and an admin panel, and each one adds design, code and testing. Scope is the biggest lever you control.
2. Platforms: iOS, Android, web, or all three
Native iOS and Android are two codebases. Cross-platform frameworks such as Flutter and React Native give you one codebase for both phones, which costs less to build and maintain when the app does not lean on phone hardware. A web app reaches every device from one codebase, but cannot sit on a home screen in the same way. We cover the trade-offs in native or cross-platform apps.
3. The backend
Almost every app needs a server side: accounts, data, business rules, notifications and an admin panel. This is the part founders forget when they compare quotes. An app with a backend is two products, and the backend often takes as long as the app. If you already have a system the app can talk to, such as a CRM or a store, the backend shrinks.
4. Integrations
Payments, maps, SMS, email, calendars, accounting, a CRM, a store. Each integration is a known cost when the service has a good API, and an unknown one when it does not. Ask your developer which integrations are routine and which are research.
5. Design
A clean, standard interface built from platform components is quick. Custom illustration, animation and a brand system take longer and need a designer. Decide early which one your users expect. A business tool can be plain. A consumer app usually cannot.
6. Compliance and security
Health data, payments, children’s data and anything regulated add requirements: encryption, audit logs, consent screens, data residency, penetration testing. They are not optional, and they are cheaper to design in than to add later.
7. Who builds it
A freelancer, a local agency, an offshore team and an in-house hire have very different rates and very different risks. Rate matters less than you think. The expensive outcome is an app that has to be rebuilt. Ask for references, look at live apps the team has shipped, and ask who owns the code when the contract ends. Our guide on dedicated team or fixed-scope project covers the engagement models.
How to estimate your own app
Write the app down as a list before you ask anyone for a price. It takes an afternoon and it changes every conversation you have afterwards.
- List every screen a user sees, and what they can do on it.
- List every type of user, including the admin.
- List every outside service the app talks to.
- Mark each item as must-have for launch, or later.
- Note any data that is regulated or sensitive.
Send that list to two or three teams and ask each for a scope, not just a number. The one that asks the most questions is usually the one that understands the work.
Ways to spend less without a worse app
- Launch a first version with the must-haves only. Our guide on how to scope an MVP explains the method.
- Use one codebase for both phones unless the app needs the hardware.
- Connect to systems you already have instead of rebuilding them.
- Use standard interface components for the first version.
- Decide what you will measure after launch, so the second version is built on data.
The costs after launch
Hosting, app store developer accounts, third-party service fees, monitoring, bug fixes, operating system updates that break things, and the feature requests that arrive the week after launch. Plan for a maintenance plan from the start. An app with nobody responsible for it ages fast.
FAQ
Can I get a fixed price for an app?
Yes, once the scope is written down in enough detail. A fixed price on a vague scope is a guess, and the gap gets closed later by cutting corners or adding invoices.
Is it cheaper to build a web app than a mobile app?
Usually, because one codebase covers every device and there is no app store review. It is the wrong choice when users need offline access, push notifications or the phone’s hardware.
Does using no-code or templates reduce the cost?
For a first version with standard needs, it can. The cost comes later, when the product outgrows the tool and has to be rebuilt. Decide with that in mind.
What should I ask an agency before I sign?
Who owns the code, what happens to the backend if we part ways, which integrations are routine, and what the plan is for the month after launch.
Next step
If you have the list, send it to us. Our mobile app development and web application development teams will reply with a scope and the questions we would ask, and our MVP development page explains how we keep the first version small.