What app development cost actually covers
When people ask about app development cost, they usually mean the price of the first production release. That release includes far more than screens: product discovery, UX and UI design, client apps, a backend and database, an admin tool, automated tests, QA, release management and the cloud setup that keeps it running.
The figures on this page are typical US-market estimates for agency-built software at blended rates of roughly $100–$200 per hour. They are planning ranges, not quotes. Two products with the same one-line description can differ by 3x once integrations, compliance and data volume are on the table.
| Tier | What it usually includes | Typical cost | Typical timeline |
|---|---|---|---|
| Simple | 5–10 core screens, standard sign-in, basic backend or BaaS, light admin, one or two integrations | $25,000–$60,000 | 8–14 weeks |
| Mid-complexity | Custom backend, payments, push notifications, role-based access, analytics, admin dashboard, 3–5 integrations | $60,000–$150,000 | 4–6 months |
| Complex | Real-time features, offline sync, multi-tenant data, compliance work (HIPAA, PCI DSS), heavy integrations, AI features | $150,000–$400,000+ | 6–12+ months |
Cost by app type: web, PWA, native and cross-platform
Platform choice is the first big multiplier. A browser-based product shares one codebase across every device, while two native mobile apps mean two client codebases, two release pipelines and two QA passes. The backend, design system and project management are shared in every case, which is why a second native platform rarely doubles the bill.
| Approach | Relative cost | Best fit |
|---|---|---|
| Web app (responsive) | Baseline; often the lowest-cost option for internal tools and B2B dashboards | SaaS products, portals, admin-heavy workflows |
| Progressive web app | Roughly baseline plus 10–20% for offline caching, installability and push | Content and commerce products that want app-like reach without store listings |
| One native app (iOS or Android) | Baseline for mobile; full tier ranges above apply | Launching on the platform where most of your users already are |
| Cross-platform app (Flutter or React Native) | Often 25–40% less than two native apps | Consumer and B2B apps that need iOS and Android with shared UI |
| Two native apps | Roughly 1.5–1.8x a single-platform build | Hardware-heavy, performance-critical or deeply OS-integrated apps |
If your users work mostly at a desk, custom web application builds often deliver the same business value for less money and faster releases. If the product depends on the camera, location, background work or push engagement, mobile is worth the premium. Our mobile-specific cost comparison goes deeper on native versus cross-platform trade-offs.
Cost by feature
Features are where estimates grow quietly. Each item below includes client UI, backend logic, testing and edge cases, which is why something that looks like one button can carry a five-figure line item.
| Feature | Typical added cost | What drives the range |
|---|---|---|
| Sign-in (email, social, SSO) | $3,000–$10,000 | Enterprise SSO (SAML, OIDC) and MFA sit at the top of the range |
| Payments and subscriptions | $5,000–$15,000 | Stripe vs in-app purchase rules, refunds, invoicing, tax handling |
| Push notifications | $2,000–$6,000 | Segmentation, scheduling and deep links into specific screens |
| In-app chat or messaging | $10,000–$30,000 | Real-time delivery, read receipts, attachments, moderation |
| Maps and geolocation | $5,000–$20,000 | Background tracking, geofencing, routing and battery tuning |
| Admin dashboard | $10,000–$30,000 | Number of roles, reporting depth, bulk actions and audit logs |
| Offline mode and sync | $8,000–$25,000 | Conflict resolution rules and how much data lives on the device |
| Third-party integration (each) | $3,000–$15,000 | API quality, documentation, sandbox access and rate limits |
| AI or LLM-powered feature | $10,000–$40,000 | Retrieval over your data, evaluation, guardrails and usage costs |
| Video calls or streaming | $15,000–$50,000 | SDK vs custom media pipeline, recording, bandwidth costs |
Where the budget goes: phases and team roles
Development is the largest share, but it is not the whole project. Teams that skip design or QA to save money usually pay that amount back later in rework and support tickets.
| Phase | Share of budget | Main outputs |
|---|---|---|
| Discovery and planning | 5–10% | Scope, user flows, architecture outline, ranged estimate, release plan |
| UX and UI design | 10–15% | Wireframes, clickable prototype, design system, handoff specs |
| Engineering (client + backend) | 50–60% | Apps, APIs, database, integrations, admin tools |
| QA and testing | 15–20% | Test plans, automated tests, device and browser coverage, regression |
| Project management, DevOps, release | 10–15% | Sprint planning, CI/CD, environments, store submission, launch support |
| Role | Typical rate | Notes |
|---|---|---|
| Product or project manager | $110–$170/hr | Often part-time on smaller projects |
| UX/UI designer | $100–$170/hr | Heaviest in the first third of the project |
| Mobile engineer (iOS, Android, Flutter, React Native) | $110–$200/hr | Native specialists usually sit at the upper end |
| Backend or web engineer | $110–$200/hr | Rates rise with cloud, data and security depth |
| QA engineer | $80–$130/hr | Automation engineers trend higher than manual testers |
| DevOps or cloud engineer | $130–$200/hr | Usually fractional; front-loaded for setup |
Timeline and how it shapes cost
Cost and calendar time are linked but not identical. A larger team can shorten the schedule, yet coordination overhead means doubling the team rarely halves the timeline. The most reliable way to ship sooner is to ship less in the first release.
| Stage | Simple app | Mid-complexity app | Complex app |
|---|---|---|---|
| Discovery | 1–2 weeks | 2–4 weeks | 4–6 weeks |
| UX and UI design | 2–3 weeks | 3–6 weeks | 6–10 weeks |
| Engineering sprints | 5–8 weeks | 10–18 weeks | 20–40+ weeks |
| QA, beta and hardening | 1–2 weeks | 3–5 weeks | 6–10 weeks |
| Launch and stabilization | 1 week | 1–2 weeks | 2–4 weeks |
Design and backend work often overlap, so the stages above add up to slightly more than the end-to-end ranges in the tier table. Fixed external dates such as a trade show or a contract renewal are worth naming early, because they shape scope more than any other constraint.
Factors that move a project within its range
- Number of distinct user roles, each with its own screens and permissions.
- Quality of the APIs you must integrate with, especially older ERP, EHR or banking systems.
- Data sensitivity and the audit, encryption and retention work that follows from it.
- How custom the visual design is compared with standard platform components.
- Expected scale at launch, which decides how much load testing and infrastructure work is needed.
Ongoing costs after launch
Software keeps costing money after release because operating systems, browsers, libraries and user expectations keep moving. Plan for these lines in your first-year budget rather than treating them as surprises.
| Item | Typical cost | Notes |
|---|---|---|
| Maintenance and updates | 15–20% of the build cost per year | OS updates, dependency upgrades, bug fixes, small improvements |
| Cloud hosting | $50–$500/month early; $500–$3,000/month growing; $3,000+/month at scale | Driven by traffic, storage, media and database size |
| Apple Developer Program | $99/year | Required to publish on the App Store |
| Google Play developer account | $25 one-time | Required to publish on Google Play |
| Third-party services | $0–$2,000+/month | Email, SMS, maps, analytics, error monitoring, search |
| Store commissions | 15–30% of digital sales | Applies to in-app digital goods and subscriptions, not physical goods |
Many teams fold these into ongoing maintenance and support plans so that security patches and OS releases are handled on a schedule instead of in a rush.
Hidden costs that catch budgets off guard
- Data migration. Moving records from spreadsheets or a legacy system often takes weeks of cleanup and mapping.
- Compliance work. HIPAA, PCI DSS or SOC 2 expectations add audit logging, encryption, access reviews and documentation.
- Content and copy. Onboarding text, legal pages, help content and store listings need an owner and time.
- Accessibility. Meeting WCAG 2.2 AA after the fact costs more than designing for it from the first wireframe.
- Usage-based APIs. Maps, SMS, AI models and video SDKs bill per use and can grow faster than revenue early on.
- Scope changes mid-build. Late changes ripple through design, code and tests; a change budget of 10–15% is a healthy buffer.
How to reduce cost without hurting quality
- Ship one platform or one cross-platform codebase first, then expand once you have usage data.
- Use managed services for authentication, payments and file storage instead of building them.
- Cut features, not testing. A smaller, well-tested release is cheaper to grow than a large, fragile one.
- Approve a clickable prototype before engineering starts so that design changes happen in hours, not sprints.
- Keep the admin tool simple at launch; internal users tolerate plain interfaces far better than customers do.
If you are validating a new idea rather than replacing a working system, start with our guide to budgeting a first release, which covers how to cut scope while protecting what users will judge you on.
How we estimate your project
We start with a short discovery phase, typically two to four weeks, to map user flows, integrations, data and risks. The output is a ranged estimate with assumptions written down, so you can see which decisions move the number up or down.
From there you choose how to buy the work. Fixed price suits a well-defined scope, while time and materials suits products that will change as you learn. We explain both in our fixed-price and time-and-materials engagement options, and you can request a ranged estimate for your app once you have a rough feature list.