How much does it cost to build an app?
Every agency answers "it depends". Here is what it actually depends on, and a free calculator to put rough numbers on your own idea.
The price is hours × rate
An app's cost is the hours it takes to design, build, test and launch, multiplied by the hourly rate of the people building it. Rates vary widely by country and by seniority, so the more useful question is: how many hours will my app take?
Try our free app cost estimator: tick your features, set a rate, and see a range.
What drives the hours
1. Features
Each feature is a small project of its own. Login is quick; chat, payments, offline sync and admin dashboards are not. Features that touch money, security or real-time data take the longest, because they need the most testing.
2. Number of screens
Every screen needs design, building, and testing on different phone sizes. A focused 10-screen app costs far less than a 40-screen one, even with the same features.
3. Platforms
Android only, Android and iOS natively, or one cross-platform codebase. Two native apps cost the most; cross-platform sits in between. (Our guide: native vs cross-platform.)
4. The backend
Most apps need a server: user accounts, a database, notifications, an API. Managed platforms like Firebase cut this work a lot for typical apps. Complex business logic still needs custom code.
5. Integrations
Every outside system, such as a payment provider, CRM, booking engine or bank connection, adds its own setup, error handling and testing. Regulated integrations like open banking take longer still.
6. Testing and project management
Budget around 20% for testing and 10% for project management on top of the build. Skipping them does not save money; it moves the cost to after launch, when fixes are more expensive.
Costs after launch
- Hosting and services: servers, databases, email, maps or AI usage, billed monthly and growing with users.
- Store fees: Google Play charges a one-time developer registration fee; Apple charges a yearly developer membership.
- Maintenance: new Android and iOS versions every year, security updates and bug fixes. A common rule of thumb is 15–20% of the build cost per year.
How to spend less without cutting quality
- Launch a smaller first version. Ship the one feature people need most, then add the rest based on real use.
- Start on one platform if your users mostly use it.
- Use managed services for login, storage and notifications instead of building them.
- Decide the screens before building. Changing designs mid-build is the most common budget leak.