Key takeaways
- A focused first version of an app costs $30,000–$80,000 with an offshore team or $100,000–$250,000 with a US agency in 2026. Clutch's pricing data puts the average mobile app project at $90,780 over about 11 months.
- Half the small businesses asking "how much does an app cost" don't need a native app. A mobile web app or PWA delivers most of the value at roughly a tenth of the price.
- Budget 15–20% of the build cost per year for maintenance, plus store fees and commissions. Your first-year true cost is the build × 1.3, minimum.
- Never accept a quote that doesn't show an hour breakdown. "Simple / medium / complex" tiers without hours behind them are marketing, not pricing.
The short answer
Every credible app quote is built from one formula: estimated hours × hourly rate + fixed costs. Fixed costs are the store fees, cloud hosting, payment processing, and third-party services — they don't shrink when you negotiate the rate.
Here's where real 2026 projects land:
| App tier | What it looks like | Timeline | Offshore team | US agency |
|---|---|---|---|---|
| MVP | 5–10 screens, one user role, login, basic backend | 2–3 months | $15,000–$40,000 | $50,000–$120,000 |
| Mid-range | Custom design, payments, push notifications, admin panel, a few integrations | 4–7 months | $40,000–$100,000 | $120,000–$250,000 |
| Complex | Real-time chat, AI features, video, multi-role permissions, offline mode | 7–12 months | $100,000–$200,000 | $250,000–$500,000+ |
| Enterprise | Compliance (HIPAA/PCI), legacy integrations, multi-platform, dedicated security | 9–18 months | $200,000+ | $500,000+ |
Clutch's 2026 pricing data says most reviewed mobile app projects fall between $10,000 and $49,999, with the average project costing $90,780 over about 11 months. The median North American project sits between $50,000 and $150,000.
That spread is why "it depends" is the industry's favorite answer — and why it's useless to you. The rest of this post makes it depend on things you can actually check.
First: the question the app shops won't ask you
Here's our disclosure up front: we're a web agency, not an app shop. We build websites, stores, and web applications. We don't make our money selling you a native app build — which is exactly why you can trust this section.
Roughly half the small-business owners who ask us "how much does an app cost" don't need a native app at all. What they actually need is one of these:
- A mobile-optimized website with booking, ordering, or account features — $4,000–$15,000 to build, works on every phone, no app store needed.
- A progressive web app (PWA) — installs to the home screen, works offline, sends push notifications, at roughly a tenth of native app cost.
You genuinely need a native iOS/Android app when: your users will open it daily (frequency justifies the download), you need deep hardware access (Bluetooth, AR, background sensors), you need offline-first field work, or you're building a consumer product where the app store is your distribution channel.
A restaurant doesn't need a $60,000 app for online ordering. It needs a fast mobile website with a prominent "Order" button. The app shops will never tell you this, because their business model depends on you not knowing it.
If you're on the fence, read our full breakdown of app vs website — it walks through the decision with real examples.
Still need the app? Let's talk about where the money goes.
What actually sets the price: the feature menu
Forget "simple / medium / complex." Price lives at the feature level. Every feature you add buys design time, development time, and testing time — and some features are shockingly expensive relative to how small they look on a screen.
| Feature | Typical cost | Why it costs that |
|---|---|---|
| User login (email + social) | $5,000–$15,000 | OAuth, session management, password recovery, security review |
| Payment processing | $10,000–$25,000 | Gateway integration, edge cases, refunds, PCI-safe handling |
| Push notifications | $3,000–$8,000 | Service setup, permission flows, segmentation |
| Real-time chat | $15,000–$40,000 | WebSockets, message history, moderation, scaling |
| Maps / location | $8,000–$20,000 | API integration, geocoding, ongoing per-request fees |
| AI features | $25,000–$80,000 | Model integration, prompt engineering, per-token running costs |
| Admin panel | $10,000–$30,000 | It's a second app nobody sees — user management, content, reports |
| Video calling / streaming | $20,000–$50,000 | Real-time infrastructure, bandwidth, device testing |
Two things founders consistently underestimate:
1. The backend is the invisible half. The app on the phone is the tip. Underneath sit servers, databases, APIs, business logic, and the admin panel your team uses daily. Backend work routinely matches or exceeds the app-side hours. When a quote seems "too cheap," the backend is usually what's missing — or what's about to arrive as a change order.
2. Buy, don't build, commodity features. Authentication, payments, chat, analytics, crash reporting — mature services exist for all of them (Firebase, Supabase, Stripe, Twilio, Stream). Building your own login system in 2026 is like manufacturing your own lightbulbs. Any quote that hand-rolls commodity features is either padding hours or stuck in 2014.
Platform choice: the $100,000 decision
This is the single biggest cost lever, and it's decided in week one:
| Approach | Relative cost | Choose it when |
|---|---|---|
| Native iOS + Android (Swift + Kotlin, two codebases) | 2× baseline | Games, AR/VR, heavy hardware integration, platform-specific polish is the product |
| Cross-platform (Flutter / React Native, one codebase) | ~0.6–0.7× of dual-native | Most MVPs and growth-stage apps — saves 30–40% with no meaningful quality loss for standard UI |
| Single platform first (iOS or Android only) | ~0.5× of dual-native | You know exactly where your users are (e.g., US consumers skew iPhone; field teams get company Androids) |
| PWA / mobile web | ~0.1–0.15× of native | Content, booking, ordering, accounts — no app-store distribution needed |
The honest default for most businesses in 2026: cross-platform (Flutter or React Native), both stores, one codebase. Going fully native on both platforms roughly doubles the project — two teams, two bug lists, two release pipelines — and the performance gap only matters for graphics-heavy or hardware-deep apps.
One 2026-specific note: AI coding assistants have genuinely shaved 15–25% off implementation time for experienced developers, and that's starting to show up in quotes.
Who builds it: the rate reality
Where the team sits moves the number more than almost anything else:
| Team model | Typical rate | Best for | Watch out for |
|---|---|---|---|
| Freelancer | $25–$150/hr | Prototypes, MVPs, narrowly scoped features | Single point of failure; you manage QA and project management |
| Offshore / nearshore agency | $30–$60/hr blended | Full builds at 40–60% below US rates | Vet ruthlessly — shipped apps and store ratings, not promises |
| US / Western agency | $100–$250/hr | Complex or regulated builds where timezone overlap and process matter | You're paying for process overhead too — make sure you need it |
| In-house team | $80,000–$180,000 salary per dev | Long-term products with continuous development | Loaded cost (benefits, management, turnover) runs ~30%+ over salary |
For context on US rates: the Bureau of Labor Statistics puts the median US software developer wage at $135,980/year (May 2025) — about $65/hour — and benefits add roughly 30% on top, bringing the loaded cost near $93/hour before recruiting, equipment, or management. A US agency charging $100–$150/hour isn't gouging; it's covering a real cost structure plus QA, design, and project management. Whether your project needs that structure is the actual question.
The cheapest quote is rarely the cheapest project. A $25/hour freelancer whose work needs a $60,000 rebuild in 18 months cost you more than the $50/hour team that shipped it right once. Ask every bidder: "Show me three apps live in the stores right now that you built."
Our fuller take on this tradeoff — written from the agency side, including when we'd tell you to hire the freelancer — is in freelancer vs agency.
What the quote doesn't include: your true first-year cost
This is where budgets actually die. The build quote is maybe 70% of your first-year spend. The rest:
- Store fees: Apple Developer Program is $99/year, every year, one account covering all your apps. Google Play is a $25 one-time registration.
- Store commissions: Apple takes 30% of digital in-app purchases and subscriptions — but the Small Business Program cuts that to 15% if your annual proceeds are under $1 million, and subscriptions drop to 15% after the subscriber's first year. Selling physical goods or real-world services (food delivery, ride-hailing)? Zero commission — Apple can only tax digital goods. Google Play runs similar tiers. Model this into pricing before launch, not after.
- Maintenance: 15–20% of build cost per year. iOS and Android ship major OS updates annually, and each one can break things. Budget 2–4 weeks of developer time per major OS release just to keep the app running — that's $5,000–$20,000/year before you add a single feature.
- Backend and infrastructure: Cloud bills start small and scale with users. Budget a few hundred to a few thousand per month for a mid-sized app, and revisit quarterly — companies overspend on cloud by nearly 30% on average.
- Payment and service fees: Stripe's 2.9% + 30¢ per card payment, Twilio's ~$0.008 per SMS segment, Google Maps' per-request pricing after the free tier.
Rule of thumb: your first-year true cost is the build quote × 1.3, minimum. If that number scares you, the project isn't ready — shrink the scope, not the budget.
How to read an app quote like an insider
You've got three quotes ranging from $35,000 to $180,000 for what sounds like the same app. Here's how to compare them:
- Demand the hour breakdown. A real quote shows hours per phase: discovery, design, app development, backend, QA, launch. "Simple / medium / complex" tiers with no hours behind them are marketing. Hours × rate should roughly equal the total — if it doesn't, ask what the gap is.
- Check what's excluded. The five classic exclusions: UI/UX design (sometimes quoted separately), backend and admin panel, QA testing, app store submission and review cycles, and post-launch support. A $40,000 quote excluding design, backend, and QA is really a $90,000 quote.
- Fixed-bid vs. time-and-materials. Fixed bids feel safe but vendors pad them 20–30% for risk — and every change becomes a negotiation. Time-and-materials is honest but requires you to manage scope. For MVPs, we prefer fixed-bid on a ruthlessly small scope; for evolving products, T&M with weekly demos.
- Read the milestone schedule. Never pay more than 20–30% upfront. Sane milestones: kickoff, design approval, working beta, store submission, launch + 30-day warranty. A vendor demanding 50% upfront is telling you about their cash flow, not your project.
- Ask for the v1 cut list. The best question you can ask any bidder: "What would you cut from v1 to ship in half the time?" Their answer reveals whether they understand product thinking or just sell hours. Every app has a version that's 50% cheaper and validates the same risk.
The budget ladder: validate before you build
The most expensive app is the one nobody wanted. CB Insights' startup post-mortems have consistently found that building something nobody wanted is a top killer — around 35% of failed startups cite it. The ladder that avoids this:
- Validate demand for under $5,000. Landing page, concierge MVP, or clickable prototype. If you can't get 100 people to say "take my money" (or at least their email), an app won't fix that.
- Build the MVP: $15,000–$50,000. One core flow, one platform approach (cross-platform or even PWA), bought-not-built commodity features. Our full playbook for scoping this is in how much an MVP costs.
- Scale what works. Add platforms, features, and polish with revenue or validated traction behind each step — not with hope.
Most founders we talk to want to start at step 2 or 3. The ones who succeed usually wish they'd spent longer on step 1.
The bottom line
An app costs $30,000–$80,000 (offshore) or $100,000–$250,000 (US agency) for a focused first version in 2026, and roughly 1.3× that in true first-year cost. The number is set by features (use the menu above), platform choice (cross-platform by default), and team location — not by the tier names on an agency's pricing page.
And the most honest advice in this whole post: make sure you need an app before you price one. Half our "app cost" inquiries end with the client saving $50,000+ by building an excellent mobile web experience instead.
Not sure which camp you're in? That's exactly what our free website audit is for — we'll tell you straight whether your idea needs an app, a web app, or just a better website. Or book a call and we'll scope it properly, with hours, not tier names.
