Practical guide · Updated July 25, 2026
How much does it cost to make an app?
A simple app can cost a few thousand dollars; a production mobile product can cost six figures. The useful answer depends on what already exists, which risks the app owns and whether you are pricing a build or the first year of operation.
Quick answer: realistic planning ranges
These planning ranges assume a competent small team, a defined outcome and production work beyond a visual prototype.
At App Release Ops, a straightforward existing web product typically starts at $1,500-$3,000 for managed mobile packaging and release. The range moves when the underlying product is not production-ready.
The six things an app budget is paying for
“Build the app” hides several different projects. A useful estimate separates them.
- Product definition: scope, user journeys, edge cases and acceptance criteria
- Design: information architecture, interaction states, responsive behavior and store assets
- Client application: web, Capacitor, React Native, Flutter, Swift or Kotlin implementation
- Backend: authentication, database, storage, APIs, jobs, notifications and admin operations
- Production readiness: security, privacy, analytics, crash reporting, payments and failure handling
- Distribution and operations: signing, testing, store review, releases, monitoring and support
A quote that includes only interface construction can look dramatically cheaper while leaving most of the launch project to the buyer.
Why an existing web app plus Capacitor is usually cheapest
If a responsive web product already works, our default is to preserve it and package it with Capacitor. Web, iOS and Android share the same product code, so the initial conversion is fast and future maintenance does not require implementing every feature three times.
Native capabilities do not automatically require a rewrite. Push notifications, camera, files, deep links, geolocation, biometrics, secure storage and in-app purchases can be connected through Capacitor plugins. A small custom Swift or Kotlin plugin can expose an app-specific SDK while the rest of the product remains web-based.
React Native, Flutter or fully native development becomes worth the additional cost when native navigation, complex gestures, background execution, sustained rendering performance or platform-specific frameworks are central to the product.
Features that move the price most
Screen count is a weak estimator. Complexity comes from states, permissions, data ownership and failure modes.
- Authentication: social sign-in, enterprise SSO, account recovery, roles and account deletion
- Payments: subscriptions, consumables, refunds, entitlements and server-side verification
- Offline use: local storage, synchronization, conflict resolution and background retry
- Real-time behavior: chat, collaboration, presence, live location or streaming updates
- User-generated content: uploads, moderation, reporting, storage and abuse controls
- Hardware: Bluetooth, HealthKit, sensors, camera pipelines or proprietary SDKs
- Regulation: health, finance, children, identity verification, audit logs or data residency
- Admin operations: support tools, refunds, moderation, content management and manual exceptions
- Localization: copy, layouts, screenshots, currencies, legal text and support across markets
Each item is affordable in isolation. Combinations create the expensive part because they multiply testing and operational paths.
Backend and infrastructure costs
An app can be cheap to download while expensive to operate. Estimate infrastructure from workload rather than user count alone.
- Database size, read/write volume and backup retention
- Image, video or document storage and delivery
- Search indexes, recommendation workloads and product catalogs
- LLM, vision, transcription or other usage-based APIs
- Scheduled jobs, webhooks and background processing
- Email, SMS, push and authentication providers
- Logging, analytics, crash reporting and alert retention
- Separate development, staging and production environments
A mostly on-device utility may operate near zero marginal server cost. A catalog, AI or media product may incur meaningful baseline spend before it has significant revenue.
Store accounts and direct launch fees
The store account itself is a small part of the budget. Apple currently lists the Apple Developer Program at $99 per membership year; Google Play lists a $25 one-time registration fee for a full-distribution Play Console account. Taxes, supported regions and account requirements can vary.
Also budget for business verification, D-U-N-S setup where required, privacy and support pages, screenshots, testing devices and the time needed to satisfy account or testing requirements.
Three example budgets
The word “app” can describe projects with very different scope.
A regulated health product, hardware companion or highly interactive consumer app can exceed these ranges because verification, native work and QA are core product requirements.
Budget for the first year
A practical first-year model is:
First-year cost = initial build + production hardening + launch + infrastructure + maintenance + corrective releases.
- Developer accounts and required third-party subscriptions
- Hosting, storage, APIs and observability
- Dependency, SDK and target-OS updates
- Store policy changes and repeated submissions
- Crash, ANR and support investigation
- At least one post-launch corrective release
- Security fixes, backup verification and operational ownership
For a small stable product, maintenance may be a few hundred dollars per month. Products with active development, heavy infrastructure or regulated operations need a real ongoing team rather than a maintenance line item.
Why the cheapest quote often becomes expensive
Low quotes are not automatically wrong. They are dangerous when the missing assumptions are invisible.
- The estimate covers a demo build but not production security
- The backend, admin panel or migration is excluded
- Only one platform or device size is actually tested
- Store submission ends at the first rejection
- Payments work only in a happy-path sandbox transaction
- Design omits empty, loading, denied, offline and error states
- Source code, signing keys or accounts remain controlled by the vendor
- No one owns the first release after launch
Compare quotes by delivered outcome and explicit exclusions, not by the number at the bottom of the proposal.
How to reduce app development cost without building junk
- Start from an existing responsive web product when possible
- Use Capacitor before funding a full mobile rewrite
- Validate the hardest native or backend requirement with a release spike
- Launch one complete user outcome instead of many partial features
- Use managed authentication, databases and billing where they reduce operational risk
- Keep web, iOS and Android behavior shared unless differentiation creates value
- Instrument activation, errors and purchases before adding growth features
- Own the store and cloud accounts from day one
- Demand a reproducible build and documented release path
The goal is not the smallest initial invoice. It is the lowest cost path to a product that can launch, learn and keep shipping.
Questions to answer before requesting an estimate
- What already exists: design, deployed web app, backend, data and users?
- Which single outcome must version 1.0 complete?
- Which native capabilities are genuinely required?
- Does the app sell digital goods, physical goods or services?
- What must work offline or in the background?
- Which countries, languages and regulated categories are in scope?
- How will support, moderation and administrative exceptions work?
- What launch date is real, and what can be removed to protect it?
- Who owns maintenance after approval?
With those answers, an estimate can describe a release. Without them, it usually describes optimism.