Guide
How much does it cost to build an app?
The factors that decide what an app costs to build and run, and how to get an estimate you can compare between developers.
"How much does an app cost?" is one of the most common questions developers get, and the honest answer is always "it depends". That is not much help when you are planning a budget. This guide explains what it depends on, so you can understand the quotes you receive and compare them properly.
Note: We have deliberately not included price figures. Rates vary widely by country, team and contract type, and any number without your scope behind it would be a guess. A clear brief gets you a real estimate.
Why quotes vary so much
If you send the same short message to three developers, you may get three very different numbers. Usually none of them is wrong: each has filled the gaps in the request with different assumptions about screens, integrations, design and quality.
The contract type matters too:
- Fixed price: an agreed scope for an agreed amount. Predictable, but the developer adds a margin for risk, and changes cost extra.
- Time and materials: you pay for the time spent. More flexible, but you need regular visibility of progress and spend.
Neither is better in general. Fixed price suits a well-defined scope; time and materials suits products that will evolve as you learn.
What drives the cost
Screens and user journeys
The number of distinct screens, and the journeys that connect them, is the biggest single driver. A booking app with search, a slot picker, checkout and an account area is a very different size from one with a single form.
Platforms
You can build for iOS, Android, the web, or several of them. Separate native apps for iOS and Android roughly mean two codebases to build and maintain. A cross-platform framework such as Flutter uses one codebase for both mobile platforms (and can also target web and desktop), which usually reduces cost for business apps without giving up a native feel.
Backend, admin panel and integrations
Most apps need more than the app itself:
- A backend that stores data and handles accounts
- An admin panel for your team to manage content, orders or users
- Integrations with payments, maps, SMS, email, your CRM or accounting software
Integrations are often where estimates differ most, because each third-party service has its own rules, limits and edge cases.
Design depth, accessibility and offline support
A clean design using standard components costs less than a fully custom visual identity with animations. Accessibility work (screen readers, contrast, text size) is worth doing and takes time. Offline support, where the app keeps working without a connection and syncs later, adds real complexity and should be decided early.
App store preparation and releases
Publishing to the App Store and Google Play involves store listings, screenshots, privacy declarations, review requirements and test releases. It is not a large part of the budget, but it is often forgotten.
Costs after launch
The build is not the last cost. Plan for:
- Hosting and third-party services: servers, databases, file storage, email, SMS, maps and payment fees. Many grow with usage.
- Platform updates: Apple and Google release new operating system versions every year and change store policies regularly. Apps need updates to keep working and to stay in the stores.
- Security fixes: libraries and frameworks receive security updates that need to be applied.
- Ongoing improvements: once real users arrive, you will want to change things. This is a good sign, and it should be in the budget.
How to lower the cost without cutting quality
- Start with an MVP. Build the smallest version that proves the idea, then improve it based on real use. See what an MVP is.
- Reuse existing services. Use established providers for payments, authentication, email and maps rather than building your own.
- Choose one codebase where it fits, such as Flutter for iOS and Android together.
- Write a clear brief. Clear requirements reduce the risk margin in every quote. Our project brief generator helps you structure one.
Getting a quote you can compare
What to include in your request
- The problem the app solves and who uses it
- The main journeys, as a short list
- Platforms you need at launch, and which can wait
- Integrations with existing systems
- Your timeline and a budget range, even if rough
- Anything you are unsure about, stated as an open question
Questions to ask every developer
- What is included in this estimate, and what is not?
- What assumptions did you make?
- How do you handle changes in scope?
- Who owns the code, the store accounts and the hosting?
- What does support look like after launch, and what does it cost?
When every developer answers the same questions about the same brief, the quotes become genuinely comparable, and the differences between them start to make sense.
- Planning
Try it yourself
- Project brief generatorAnswer a few questions and get a structured software brief you can share with any developer, including the open questions you still need to answer.
- MVP scope plannerSort your feature list into must, should, could and won’t, size each one, and see what a genuinely minimal first release looks like.
Want a written estimate for your app?
Share a short brief. We reply with questions and an estimate broken down by feature.
Keep reading
- How to choose a custom software development companyWhat to look for, what to ask and which warning signs to watch for when choosing a company to build your software.
- MVP development cost: what founders should budgetWhat goes into the cost of an MVP, the line items founders forget, and how to plan a budget that leaves room to improve after launch.
- What is an MVP in software development?What a minimum viable product is, what it is not, and how to decide what goes into the first version of your software.