Most of the people asking this question are not building a startup. They have been told to get an app built, and they need a number they can defend to someone who will ask where it came from. The ranges above are the easy part. What determines whether your budget holds is what sits underneath them, and that is what this guide breaks down.
Every vendor publishes a range table. They disagree with each other, which is why you are still reading. This guide explains the variance instead of adding to it.
Key takeaways
- Simple apps cost $20,000 to $60,000. Enterprise and AI-driven platforms start at $350,000.
- Team location is the single biggest lever. Rates run $20 per hour offshore to $250 per hour in North America.
- Cross-platform frameworks cost 30% to 40% less than two separate native builds.
- Internal workforce apps cost less to design and more to integrate than consumer apps. Most guides ignore this entirely.
- Post-launch maintenance runs 15% to 20% of build cost every year.
- Security, DevOps, compliance and store fees add 25% to 35% on top of the development quote.
- An MVP validates the core hypothesis before you commit the full budget.
How much does mobile app development cost in 2026?
Complexity sets your bracket before any other decision does. The table below is the reference point for everything else in this guide, and every other figure here reconciles against it.
| App type | Examples | Engineering hours | Cost range | Timeline |
| Simple | Calculator, to-do, static information app | 400 to 800 | $20,000 to $60,000 | 2 to 4 months |
| Mid-complexity | eCommerce, social, booking | 800 to 2,000 | $60,000 to $150,000 | 4 to 8 months |
| Complex | Fintech, healthcare, marketplace | 2,000 to 5,000 | $150,000 to $350,000 | 8 to 14 months |
| Enterprise or AI | Custom ERP, AI-driven platforms | 5,000 to 10,000+ | $350,000 to $500,000+ | 12 to 24 months |
How to read this table. The ranges assume a blended delivery rate of $70 to $75 per hour, which is the hybrid model most teams now use: senior onshore product and architecture leads paired with vetted offshore engineering. A fully US-based team at $130 to $250 per hour roughly doubles to triples every figure above. An entirely offshore team at $20 to $50 per hour lands below them. Multiply the hours column by your own expected rate and you have your own version of this table.
That is the first reason vendor quotes differ by 3x on identical scope. It is rarely the scope.
What complexity actually means
Low complexity. Static content, simple user accounts, basic forms. No custom backend logic. Standard libraries handle most of the work.
Mid complexity. Payment gateways, push notifications, geolocation, role-based access control. Each of these adds 40 to 80 hours of dedicated development and users now expect all of them.
High complexity. Real-time sync, AI-powered recommendations, multi-tenant architecture, advanced security layers. These need specialist senior engineers and a separate scoping conversation before anyone quotes a number.
If you are building in a regulated vertical, complexity is set by the compliance requirement rather than the feature list. See our fintech app development cost guide and banking mobile app development cost for feature-level breakdowns.
What does an internal or workforce app cost compared to a consumer app?
An internal app with the same feature count as a consumer app usually costs less to design and more to build. Most cost guides only price consumer apps, which is why operating businesses consistently budget these wrong.
| Cost area | Consumer app | Internal or workforce app |
| UI/UX design | Higher. Visual polish and onboarding drive adoption and retention | Lower. Users are trained and required to use it. Function beats polish |
| User acquisition and ASO | $5,000 to $20,000 at launch minimum | Zero. Distribution is internal, often via MDM rather than app stores |
| System integration | Low. Usually a handful of third-party APIs | High. This is where the budget goes. ERP, EHR, WMS, payroll and HRIS connections |
| Offline capability | Often optional | Frequently mandatory for field, floor and warehouse use |
| Access control | Simple user accounts | Role-based permissions, SSO, audit trails. $3,000 to $20,000 |
| Scale | Must handle unpredictable public load | Known, bounded user count. Cheaper infrastructure |
| Device management | Users bring their own | Ruggedised hardware, kiosk mode, MDM enrolment |
What this means for your budget. A workforce app with 2,000 known users and three system integrations commonly lands in the same $150,000 to $350,000 bracket as a complex consumer app, but the money sits in different places. Shift budget out of design and acquisition and into integration, offline sync and access control.
The common planning error. Teams scope an internal app against consumer app benchmarks, allocate most of the budget to design and front-end work, then discover in month four that connecting to the existing ERP is the actual project. Price the integrations first. See the integration section below for what each connection typically adds.
How to estimate mobile app development cost
Start with the hours, not the price. Hours are a property of your scope and they stay roughly constant whoever builds it. Rate is a commercial decision you make separately.
The hours and rate formula
Total development hours x hourly rate = development cost
A 1,000-hour build at $35 per hour costs $35,000. The same 1,000 hours at $150 per hour costs $150,000. Identical scope, identical output, 4x the invoice. This excludes maintenance and post-launch work.
The hours column in the complexity table above is your starting estimate. Refine it by counting integrations, user roles and compliance requirements, which are the three things that move hours most and the three things initial quotes most often under-count.
The full budget formula
Development is roughly 65% to 75% of what you will actually spend in year one.
(development hours x rate) + design + QA + DevOps + compliance + year-one maintenance = true total cost
Budget the right-hand categories as line items from the start. Folding them into a single “development” number is how a project that quoted at $200,000 closes the year at $280,000 without anyone doing anything wrong.
Mobile app development cost by platform
Platform choice changes both the build cost and the long-term cost of owning the product. Our mobile app development services cover all five routes below, including iOS, Android and cross-platform builds.
| Platform | Cost range | Best for | Trade-off |
| Native iOS (Swift) | $40,000 to $200,000+ | Performance-critical apps, deep hardware access, higher-spending user base | Needs a separate Android build for full market reach |
| Native Android (Kotlin) | $35,000 to $180,000+ | Largest global reach, emerging markets, device-specific hardware | Fragmentation adds QA time and lengthens the testing cycle |
| Cross-platform (Flutter, React Native) | $30,000 to $130,000+ | Most products. One codebase ships both platforms | Slightly lower performance on graphics-heavy or animation-rich work |
| Hybrid | $30,000 to $80,000 | Content-led products wrapping an existing web app | Limited native feel, constrained hardware access |
| PWA | $15,000 to $60,000 | Content-heavy products, internal tools, no app store dependency | Restricted camera, GPS and Bluetooth access. No store distribution |
When native is worth the premium
Choose native when performance is the product: real-time video processing, AR, intensive graphics, or deep integration with platform-specific hardware. If you cannot name the specific capability that requires it, you probably do not need it.
When cross-platform is the right call
Cross-platform saves 30% to 40% against two native builds and is the default for most business applications, MVPs and internal tools. A Flutter app needs Dart-fluent engineers; a React Native app draws from the much larger JavaScript talent pool, which matters for your hiring cost later. Our mobile app development frameworks guide compares them in depth.
For platform-specific breakdowns, see our Android app development cost, iOS app development cost and hybrid app development cost guides.
What five real builds cost and why
Range tables are easy to publish. Here is what projects we actually delivered cost, and what drove each one into its bracket.
| Project | Industry | App type | Bracket | Primary cost driver |
| Vitalog | Healthcare | Complex cross-platform | $150K to $350K | Dual patient and clinician interfaces, compliance, real-time communication |
| PreCheck | Healthcare and HR tech | Mid to complex specialised | $150K to $350K | HIPAA architecture and live licensing-board integrations |
| TGS | Transportation and infrastructure | Enterprise operations | Upper complex | Integration with existing operational systems, two distinct user audiences |
| Reel Champ | Creator economy | Mid-complexity consumer | $60K to $150K | Payment splitting and real-time content delivery |
| Roam Trips | Travel | Mid-complexity consumer | $60K to $150K | Geolocation and social graph, scoped MVP-first |
| Vidan AI | Security and enterprise AI | Enterprise AI platform | $350K+ | Custom computer vision pipeline, multi-camera orchestration, ongoing model retraining |
What the pattern shows
Industry moves cost independently of features. PreCheck is a background screening app. Built for a general market it would cost $60,000 to $100,000. Built for healthcare, where HIPAA, licensing-board integrations and audit trails apply, the same feature set costs two to three times that.
Integration cost is invisible until the architecture phase. TGS needed real-time reporting, compliance tracking and connections into systems that were already running. None of that appears in a feature list. All of it appears in the bill. On the TGS platform, task automation reduced manual operational work by 60%, which is the return that justified the integration spend.
Scoping MVP-first is a budget decision, not a product compromise. Roam Trips launched with trip planning and sharing, deferring discovery and monetisation to phase two. Every feature deferred is budget held back for a decision made with evidence rather than assumption.
AI platforms sit above $350,000 for structural reasons. Vidan needed a custom computer vision pipeline, real-time streaming infrastructure and model retraining as conditions change. Those components do not exist off the shelf, and the retraining is a permanent operating cost rather than a one-off build cost.
Mobile app development cost by industry
Regulatory requirements, data sensitivity and integration demands vary more by vertical than feature lists do.
| Industry | Key cost drivers | Cost range | Standard |
|---|---|---|---|
| Healthcare and telemedicine | HIPAA, EHR integration, video, security | $150,000 to $500,000+ | HIPAA |
| Fintech and banking | PCI DSS, KYC and AML, real-time transactions, fraud detection | $200,000 to $600,000+ | PCI DSS, SOC 2 |
| eCommerce and marketplace | Payment gateways, catalogue, search, logistics | $80,000 to $300,000 | PCI DSS |
| Food delivery | Real-time GPS, driver app, restaurant dashboard | $80,000 to $200,000 | GPS, PCI |
| Fitness and wellness | Wearable sync, AI coaching, subscription billing | $60,000 to $200,000 | GDPR |
| Taxi and ride sharing | Driver and rider apps, live tracking, payments | $100,000 to $350,000 | COPPA if minors |
| Gaming | Physics engine, multiplayer, in-app purchases, ad SDK | $50,000 to $500,000+ | COPPA if minors |
| Enterprise and white label | Multi-tenant, SSO, ERP integration, admin panels | $200,000 to $1M+ | SOC 2, GDPR |
What does integrating with an existing ERP, EHR or warehouse system add?
This is where mid-market app budgets break. Integration is rarely in the first quote and it is frequently the largest single line in the final one.
| Integration | Typical added cost | What drives it |
|---|---|---|
| Modern REST or GraphQL API with documentation | $5,000 to $15,000 | Mapping, error handling, retry logic |
| ERP (SAP, Oracle, Dynamics, NetSuite) | $25,000 to $100,000+ | Middleware, data model translation, vendor licensing, change control |
| EHR (Epic, Cerner, Meditech) via HL7 or FHIR | $30,000 to $120,000+ | Standards mapping, sandbox access, hospital IT review cycles, audit requirements |
| Warehouse or inventory (WMS) | $20,000 to $80,000 | Real-time sync, offline reconciliation, barcode and scanner hardware |
| Payroll or HRIS | $10,000 to $40,000 | Sensitive data handling, approval workflows |
| Legacy system with no API | $40,000 to $150,000+ | Database-level integration, screen scraping or a custom middleware layer |
The three questions that set the cost. Does the system have a documented modern API? Who owns the change-control process on their side? Is the data sync real-time or batch? Real-time against a legacy system with no API and a slow change board is the most expensive combination in enterprise mobile development.
Budget the discovery. Two to four weeks of integration discovery before the build starts costs $8,000 to $25,000 and is the cheapest insurance available on a project of this shape. Teams that skip it find out in month four.
If integration is the centre of your project rather than an attachment to it, our data engineering and AI integration services may be the more accurate starting point than a mobile build.
What does UI/UX design cost?
Design is a cost driver on consumer apps and a cost control on internal ones. Price it according to which you are building.
| Design phase | Cost range | What it covers |
|---|---|---|
| UX discovery | $5,000 to $25,000 | User research, personas, journey maps, wireframes |
| Wireframing and prototyping | $3,000 to $8,000 | Flow validation before development begins |
| Visual design | $5,000 to $15,000 | Component library, branded UI, motion design |
| Design system | $8,000 to $20,000 | Shared tokens and patterns, faster future development |
| MVP design package | $15,000 to $35,000 | Focused scope, only the flows users need |
A design system costs more up front and reduces the cost of every subsequent release. Worth it if you plan more than two major versions. See our UI/UX and brand design work.
What does an MVP cost, and should you start there?
An MVP typically costs $20,000 to $60,000. It is not a stripped-down version of your app. It is a focused one, built to test the core value proposition with real users before the full budget is committed.
- Define the single core problem the app solves. Cut everything else from scope.
- Map the minimum user journey from onboarding to the moment the user gets the value.
- Build wireframes and a clickable prototype. Test with 20 to 50 target users before a line of code is written.
- Develop only the features users actually touched during prototype testing.
- Launch to 500 to 2,000 users, enough for a meaningful signal.
- Measure retention and activation. Use those numbers to plan the next sprint or the next funding round.
For internal apps, run the same process with one department before rolling out company-wide. See our MVP development cost guide.
What do AI features add to app development cost?
AI is now a standard line item rather than a premium add-on. Scope and price it separately so it does not disappear inside a vague “smart features” entry.
| AI feature | Description | Added budget |
|---|---|---|
| Recommendation engine | Personalised content or product feeds | $20,000 to $60,000 |
| Natural language processing | Chatbots, smart search, sentiment analysis | $25,000 to $80,000 |
| Computer vision | Image recognition, AR, OCR | $30,000 to $100,000 |
| Predictive analytics | Churn prediction, behavioural modelling | $15,000 to $50,000 |
| AI personalisation | Dynamic UX, adaptive content flows | $20,000 to $70,000 |
| AI layer on an existing app | Adding intelligence to a live product | $30,000 to $120,000 |
Custom models carry ongoing retraining and inference costs that API-based approaches do not. Budget for both the build and the running cost. See our AI development cost analysis and our guide to integrating AI into an existing app.
How does team location change your cost?
The largest lever in this guide. A decision here can halve or double your total spend.
| Region | Hourly rate | Strengths | Risks |
|---|---|---|---|
| North America | $130 to $250 | Quality, timezone, communication | Highest cost |
| Western Europe | $80 to $150 | Strong QA culture | High cost |
| Eastern Europe | $40 to $80 | Deep technical talent | Timezone gaps |
| Latin America | $35 to $70 | Nearshore, cultural fit | Talent scarcity in some specialisms |
| South and Southeast Asia | $20 to $50 | Cost efficiency, large talent pool | Communication overhead, timezone |
The cheapest rate is rarely the cheapest outcome. Rework, specification overhead and management time close much of the gap. Most high-performing teams run a blended model: onshore product and architecture ownership, offshore execution. That is the $70 to $75 blended rate the cost table at the top of this guide assumes.
If you are evaluating by geography, see our vendor comparisons for the USA, Houston, Dallas, Austin and Chicago.
How does your tech stack affect the budget?
Stack decisions made in week one compound across a three-year product lifecycle.
| Layer | Common choices | Budget impact |
|---|---|---|
| Mobile framework | Swift, Kotlin, Flutter, React Native | 30% to 40% saving with cross-platform versus dual native |
| Backend | Node.js, Python, Go, Rails | $15,000 to $80,000 depending on microservices versus monolith |
| Cloud infrastructure | AWS, GCP, Azure, Firebase | $200 to $5,000 per month at launch, scales with traffic |
| Database | PostgreSQL, MongoDB, DynamoDB | Minimal up front. Real-time databases add $5,000 to $20,000 in setup |
| AI and ML | TensorFlow, PyTorch, hosted model APIs | $20,000 to $150,000+ depending on custom versus API-based |
| Authentication | Auth0, Firebase Auth, enterprise SSO | $3,000 to $20,000. Enterprise SSO sits at the top of that range |
| Payments | Stripe, Braintree, custom gateways | $5,000 to $25,000 plus ongoing transaction fees |
| DevOps and CI/CD | GitHub Actions, Jenkins, Fastlane | $5,000 to $15,000 setup, reduces long-term maintenance |
What are the hidden costs of app development?
The quoted price is not the final price. These categories are usually excluded from initial proposals, not through dishonesty but because they cannot be estimated without knowing your infrastructure and compliance position. Together they add 25% to 35% on top of the development quote.
Security and compliance
GDPR, HIPAA and SOC 2 add $10,000 to $40,000 to any project handling personal data. Penetration testing runs $5,000 to $20,000 per round, with annual reviews after that. For healthcare products, HIPAA-aligned development needs its own budget line from day one.
Infrastructure and DevOps
Cloud hosting starts at $200 to $2,000 per month at launch and scales with users. A CI/CD pipeline adds $5,000 to $15,000 up front. Skipping it creates technical debt that costs several times the original setup to unwind.
App store fees
Apple charges $99 per year for a developer account. Google charges $25 once. Review adds one to three days to every update cycle. In-app purchases and subscriptions carry a 15% to 30% platform cut, which belongs in your financial model rather than your build budget.
Post-launch maintenance
Budget 15% to 20% of total build cost per year. This covers OS update cycles, new device compatibility, security patches and the minor iterations users expect without filing a ticket. See our app maintenance costs guide and mobile app QA testing guide.
Third-party APIs and SaaS fees
Every integration carries an ongoing licence cost. SMS, payments, mapping, search, analytics and monitoring services all charge monthly and all scale with your user base. Build a 36-month projection before committing to an integration-heavy architecture.
Launch and marketing
Consumer apps need $5,000 to $20,000 minimum for app store optimisation and paid acquisition. Internal apps need none of this and instead need change management and training time, which comes out of someone’s operating budget rather than the project budget. See our guide on how to launch an app.
Why did two vendors quote me 3x apart?
If you are holding two proposals with a large gap, the scope is usually not the reason. Work through these five in order.
1. Different blended rates. The most common cause and the easiest to check. Ask both vendors for estimated hours, not just price. Identical hours at $45 and $150 per hour produces a 3x gap with no difference in what gets built.
2. Different boundaries on the word “development”. One quote includes QA, DevOps setup, deployment and a warranty period. The other quotes engineering hours alone and invoices the rest later. Ask each vendor explicitly which of the hidden-cost categories above are inside the number.
3. Different assumptions about integration. If one vendor has asked detailed questions about your existing systems and the other has not, the one asking questions has priced the integration and the other has not discovered it yet. The gap will close after signature, in the wrong direction.
4. Different seniority mix. A team of five mid-level engineers and a team of two seniors plus three juniors quote very differently for the same hours. Ask for the proposed team composition and the rate per role.
5. Different definitions of done. Production-ready with monitoring, CI/CD, documentation and handover is a meaningfully different deliverable from a working build. Both are legitimate. Only one of them is what you probably assumed.
What to do with the answers. Normalise both quotes onto the same hours, the same inclusions and the same definition of done, then compare. In most cases the gap drops below 1.5x, and what remains is a real quality or risk difference you can now actually evaluate.
Fixed price, time and materials, or dedicated team: which protects your budget?
The engagement model decides who carries the risk of being wrong about scope. That is a budget question before it is a legal one.
| Model | How it works | Protects you when | Costs you when |
|---|---|---|---|
| Fixed price | Agreed scope, agreed price | Scope is genuinely stable and fully specified | Scope changes. Every variation becomes a change order and a negotiation. Vendors price contingency into the number, so you pay for risk whether or not it happens |
| Time and materials | Pay for hours worked | Scope will evolve, which it usually does | Nobody is accountable for the total. Needs an engaged product owner on your side and a cap |
| Dedicated team | Fixed monthly cost for a named team | The work runs past one project and you want continuity and retained knowledge | Utilisation drops. You pay for the team whether or not the backlog justifies it |
| Staff augmentation | Named engineers into your existing team | You have the management capacity and want direct control | You carry delivery risk entirely |
The practical answer for most mid-market builds. Fixed price the discovery and design phase, where scope genuinely can be pinned down. Move to time and materials with a cap, or a dedicated team, for the build, where it cannot. A fixed price on an unspecified build is not budget protection. It is a contingency premium plus a change-order process.
What to insist on regardless of model. Milestone-based billing tied to deliverable acceptance rather than calendar dates, written IP ownership from day one, and a named technical point of contact. Liquid Technologies runs all four models. See our engagement options and our guide to outsourcing app development.
What you need ready before a vendor can quote accurately
Vendors quote vaguely because they are given vague inputs. Bring these nine things and the range you get back will narrow considerably.
- A feature list, written as user actions. “A driver can submit a damage report with photos from offline” beats “reporting module”.
- User roles and counts. How many distinct permission levels, and roughly how many users in each.
- The systems it must connect to. Name them. For each, say whether it has a documented API and who owns change control on that side.
- Your compliance position. HIPAA, SOC 2, GDPR, PCI DSS, or none. This moves cost more than any individual feature.
- Platform decision or the constraint behind it. If you do not know, say which devices your users actually carry.
- Offline requirement. Yes or no. This is a significant architecture decision, not a feature toggle.
- Existing design assets. Brand guidelines, a design system, or nothing.
- Your timeline and what drives it. A real external deadline changes the team shape and therefore the price.
- Your budget range. Withholding it does not get you a better price. It gets you a quote scoped against the wrong assumptions.
If you have most of this, you are ready for a scoped estimate rather than a ballpark. If you have none of it, a short discovery engagement will produce it faster and cheaper than three rounds of vendor conversations will.
How to present an app budget to your CFO
The person who signs will not read this guide. They will read one slide. Structure it like this.
1. Lead with the operating problem, in money. Not “we need an app”. Instead: the manual process costs X hours per month across Y people, which is $Z annually. Approvers fund problems with a cost attached.
2. Give one number with a range, not a point estimate. “$180,000 to $240,000 for the build” is credible. “$212,000” invites the question of how you know, and you do not.
3. Show the three-year cost, not the build cost. Build, plus 15% to 20% annual maintenance, plus infrastructure and licensing. A CFO who discovers year two costs after approving year one will not approve the next project.
4. Name what is excluded. Explicitly listing what the number does not cover is the single thing that most increases a finance reviewer’s confidence in the number itself.
5. State the phase gate. “We commit $35,000 to discovery and design. At that point we will have a firm build estimate and either proceed or stop.” This converts one large irreversible decision into two smaller reversible ones, which is far easier to approve.
6. Attach one comparable. A real project of similar shape with its cost. The project table earlier in this guide is built for exactly this purpose.
What approvers push back on. Point estimates with no range, build costs with no run costs, benefits with no measurement plan, and any timeline presented as a guarantee. Expect all four and prepare answers before the meeting rather than during it.
How Liquid Technologies scopes and prices app projects
We score every proposed feature on three axes before it enters a quote: user impact, revenue or operational value, and development effort. Features that score low on the first two and high on the third get cut. That is why our estimates tend to come back smaller than the brief that produced them.
- Scope before price. Every scope decision traces to a measurable product or operational goal. If a feature cannot be tied to one, it does not enter the estimate.
- Milestone-based billing. Costs are explained before the project starts and billed against deliverable acceptance, not calendar dates.
- QA from sprint one. Testing starts with the first sprint rather than after the final build.
- Integration discovery up front. On any project touching an existing system, we price the integration before we price the app.
- Post-launch ownership. Teams are structured to act on real user data after launch, not to hand over and leave.
We work with enterprises across healthcare operations, transportation, energy and manufacturing, and we are ISO 27001 certified.
In conclusion
Mobile app development cost is not a fixed number. It is the output of decisions you make before anyone writes code: complexity, platform, team model, integration surface and compliance posture. Teams that hold their budgets are not the ones with the largest budgets. They are the ones who priced the integrations early, named what was excluded, and validated assumptions before committing the full spend.
Sources
- Grand View Research, Mobile Application Market Size Report. Global mobile app market valued at approximately $252 billion, projected to exceed $626 billion by 2030 at a CAGR above 14%. Link
