How this calculator works
App cost is hours multiplied by rate. Everything else is a way of estimating hours. This tool starts from a base hour count for the scope you chose, adds hours for each feature, multiplies for platforms and design level, then adds web and backend work on top. The rate comes from where the team sits.
hours = (base[scope] + sum(feature hours)) x platform multiplier x design multiplier + web/backend hours
cost = hours x blended hourly rate[region]
range = cost x 0.8 to cost x 1.25
weeks = hours / (team size x 32 productive hours a week), minimum 6
The numbers behind each term:
| Term | Values used |
|---|
| Base hours by scope | MVP 450, Standard 900, Complex 1,700 |
| Feature hours | Accounts 40, social login 24, payments 60, subscriptions 60, chat 90, maps 50, push 20, media upload 70, AI feature 120, offline 60, languages 40, analytics 16 |
| Platform multiplier | Single platform 1.0, cross-platform 1.25, two native codebases 1.8 |
| Design multiplier | Template 0.9, custom 1.0, premium 1.2 |
| Add-ons | Web app 260, admin panel 140, custom backend and API 200 |
| Blended hourly rate (USD) | US and Canada 120, UK and Western Europe 95, Eastern Europe 50, Latin America 45, India 30 |
| Team size for timeline | MVP 2.5, Standard 3.5, Complex 5 people |
These are the assumptions we use when scoping our own builds. They are mid-market agency figures. A freelancer will quote under them and a top-tier consultancy will quote two to three times over them for the same hours.
A worked example
A standard app, iOS and Android in React Native, custom design, with accounts, payments, push and chat, built by a team in India:
- Base 900 + features (40 + 60 + 20 + 90 = 210) = 1,110 hours
- x 1.25 for cross-platform, x 1.0 for custom design = 1,388 hours
- x $30 an hour = about $41,600, range $33,000 to $52,000
- 1,388 hours across 3.5 people at 32 productive hours a week = about 12 weeks
The same app from a US team at $120 an hour comes out near $167,000. The hours do not change. Only the rate does, which is why team location is the biggest single lever on the number.
What is not in this number
- Apple Developer Program ($99 a year) and Google Play ($25 once).
- Third-party services at scale: maps, SMS, video, AI model calls, hosting. Small at launch, real at 50,000 users.
- App store commission on revenue: 15% or 30% depending on programme and year. There is a separate app store fee calculator for that.
- Marketing. A build with no launch plan is the most common way to spend this money and get nothing back.
- Maintenance after launch. Budget 15% to 20% of the build cost a year for OS updates, bug fixes and small changes. The calculator shows 18%.
How to bring the number down without hurting the app
- Cut to one job. An MVP with one user type and one core flow costs a third of a standard app and tells you whether anyone wants it.
- Cross-platform first. React Native or Flutter covers both stores from one codebase at 1.25x, against 1.8x for two native builds. Go native later only if you hit a real limit.
- Use a backend service. Firebase or Supabase for auth, database and storage removes about 200 hours of custom backend work at MVP stage.
- Template the design, brand the details. A clean template with your colours, type and icon set reads as custom to users and saves about 10%.
- Phase the feature list. Ship, measure, then build the next feature against usage data. Half of planned features are never built once real users are in the app.
Questions people ask
How accurate is this estimate?
It is a scoping estimate, accurate to the range it shows. A fixed quote needs a written scope, screens and an API list. Use this number to decide whether to proceed and to sanity-check quotes, not as a contract price.
Why is the India rate so much lower than the US rate?
Labour cost. The hours to build a feature are the same anywhere. What changes is what an experienced engineer costs per hour in that market. Quality varies by team, not by country, so judge a team on shipped apps and references, not the rate alone.
Should I build native or cross-platform?
For most apps, cross-platform. React Native and Flutter cover both stores from one codebase with near-native performance. Go native when you need heavy graphics, AR, or deep hardware access, or when you already have separate iOS and Android teams.
How long does it take to build an app?
An MVP is usually 8 to 12 weeks. A standard app is 12 to 20 weeks. Complex products run 6 months or more and should be phased. The calculator estimates from hours divided by team capacity.
What does it cost to maintain an app after launch?
Plan for 15% to 20% of the build cost per year. That covers iOS and Android updates, dependency upgrades, bug fixes and small improvements. It rises if you add features or scale to many users.
Can I get a fixed price from ApsteQ?
Yes. Send the scope through the app development intake and you get a fixed-price proposal with a timeline. ApsteQ builds in-house and also markets the app after launch, so the estimate covers both when you want it to.
Sources
Last reviewed 11 September 2026. Formulas and benchmarks are published on the page so you can check them. This tool gives estimates, not quotes.
