Intro: the "5 agencies, 5 different prices" fallacy
80% of mobile-app-quote shoppers run into this: the same brief sent to 5 agencies returns proposals with a 10× spread between low and high. "The market is unpredictable."
The real fix: clarify the 7 items that set the price. With a vague brief, agencies pile on a risk premium and prices balloon; with a clear brief, prices speak in a 2× band. This article gives concrete ranges per item + how each affects the total.
Reference baselines for 2026: senior mobile developer day rate $200-500; mid-level $120-250. Project total = man-days × rate + design + QA + project management + infrastructure.
1. Scope: screens + user roles + workflows
Over half of cost is set by scope. No matter how slick the design, a 15-screen app costs 3-4× less than a 50-screen one.
Typical scope ranges (USD): small MVP (8-15 screens, single role, simple auth) ~$10-25K; medium (20-40 screens, 2-3 roles, payments + notifications) ~$30-70K; large (50+ screens, multi-role, live data, complex flows) ~$80-300K.
Each user role grows scope geometrically. "Customer + Admin + Field Staff + Manager" = 4 roles = 4 permission levels + 4 UI testings + 4 documentations. Each extra role adds 20-30% to the project.
Workflow complexity: a single linear flow (signup → search → buy) is simple. Branching flows (5 different flows depending on user state) are complex. Branching multiplies cost by ~1.5× per layer.
2. Backend: from scratch, existing, or BaaS?
Three scenarios: (a) existing REST/GraphQL API means no backend cost; the mobile team focuses on integration. (b) BaaS (Firebase, Supabase) cuts backend cost 30-50% but increases vendor lock-in. (c) Custom backend from scratch is 40-60% of total project cost.
Custom backend typical cost: a mid-sized SaaS API ~$15-40K (auth, CRUD, payments, notification service, admin panel). Mobile + custom backend together = ~$50-130K band.
Decision matrix: BaaS is ideal in MVP — speed + low cost. Migrating to a custom backend after the product is validated, 6-12 months in, makes sense. Writing a custom backend early wastes 30-40% of investment.
Hybrid: start MVP on Firebase → migrate critical pieces to Postgres + Node.js after 1000+ users. The plan must be set on day 1; bolting it on later doubles the cost.
3. Third-party integrations: not "a few line items"
Typical integrations in modern mobile apps: payments (Stripe / iyzico / PayTR), push notifications (FCM + APNs), analytics (Mixpanel / Amplitude), crash reporting (Sentry / Crashlytics), auth (Apple / Google / Facebook OAuth), maps (Google Maps / Mapbox), chat (PubNub / Pusher), video (Mux / Vimeo / Cloudflare Stream).
Each integration averages 1-3 weeks of implementation + testing. A 5-integration project = 5-15 weeks of extra work = +$15-40K. If this isn't in the brief, the proposal will surprise.
Common hidden cost: integration providers' monthly fees. Stripe 2.9% + $0.30 per transaction; Mapbox $50-500/month; Mixpanel $100-1000/month depending on scale. These aren't engineering cost but ongoing operations.
AI integration (OpenAI, Claude, Gemini): MVP implementation +$5-15K. Monthly API cost varies $500-50,000 depending on usage; pre-estimate is required.
4. Cross-platform vs native: 30-50% cost difference
Cross-platform (Flutter, React Native): single codebase → iOS + Android. Cost advantage 30-50%. One cross-platform team replaces two native teams. Scenarios: small-to-medium scale, B2B, content-heavy, speed-priority products.
Native (Swift / Kotlin): separate code for each platform. Cost 1.5-2×. Pros: performance, full native API access, fast adoption of new Apple/Google features. Scenarios: games, AR/VR, video editing, real-time data (live streams), high-performance graphics.
Hybrid: main app cross-platform, critical module native (e.g., video editor Native, rest in Flutter). This fits most mid-large projects; cost advantage preserved, performance solved point-by-point.
Decision drivers: team skills (RN if you have a React team, Native if you have iOS/Android engineers), 5-year maintenance cost, migration ease. The wrong call shows up in year 2 — maintenance cost doubles.
5. Testing + GDPR + security: not "bonus" — required
Testing cost is 15-25% of project price. Manual QA (1 QA × project length), automated testing (unit + widget + integration), beta testing (TestFlight / Firebase App Distribution).
Skipping tests: 2-4 weeks of intense bug fixing post-launch, 30%+ App Store rejection risk, 2-star average user reviews, poor retention. Testing = insurance; cut it and the bill comes later.
GDPR/KVKK + security: mandatory for any app handling personal data. TLS 1.2+, AES-256, password hashing (bcrypt), audit logs, privacy policy, cookie/permission flows. This package adds +$5-15K.
Sector-specific add-ons: healthcare (HIPAA), finance (PCI-DSS, banking regulator), public sector (national digital transformation). Each standard inflates cost 20-40%; surprise if not budgeted upfront.
6. Post-launch maintenance: don't ignore 5-year TCO
Initial delivery is 50% of total cost; maintenance is the next 50% (over 5 years). If this isn't discussed during the proposal, it surfaces 6 months in.
Typical maintenance items: bug fixes (critical 24h / normal 5-day SLA), iOS + Android version updates (yearly mandatory), 3rd-party SDK updates, server-side maintenance, App Store / Play Store annual fees.
Monthly maintenance package ranges: small app (1-5 hrs/week) ~$1-2.5K/month; medium (5-15 hrs/week) ~$3-7K/month; large (15-40 hrs/week) ~$8-20K/month.
5-year TCO example: $50K initial delivery + $4K/month × 60 months = $290K. Maintenance is 5× the initial investment. That's why the quality of the first delivery (testing, documentation, architecture) is the main driver of maintenance cost.
7. Healthy proposals: phased, not single line
A "$500K, 12-month" single-block proposal is risky — for the agency (scope changes = our cost) and for the client (what if surprises?).
Right structure: phased proposal. Phase 1 (MVP) 6-8 weeks, fixed price (e.g., $30K); Phase 2 (Growth) 4-8 weeks, decided after phase 1 (e.g., $20-50K band); Phase 3 (Scale) 3-6 months, planned with usage data.
This structure de-risks both sides: the client hits a "continue / stop" gate at every phase. The agency works on scope shaped by market data; not a forecast contract.
Typical 5-year totals: small MVP ~$60-100K; mid-size product ~$150-300K; large product (10+ team, 100K+ users) ~$500K-1.5M. About 50% of these numbers is maintenance + growth.
Conclusion: brief clarity halves the price
Mobile app cost is the sum of 7 items: scope + backend + integrations + native need + testing/GDPR + maintenance + phasing. Miscalculate any item and the price either inflates or detaches from reality.
On the client side, "brief clarity" cuts agencies' risk premium in half. A brief that filled the 6 sections from the "how to prepare a project" article will get 5 agencies bidding on the same baseline.
If you want a healthy proposal for your mobile app project, get in touch via our mobile app development page — a detailed 7-item breakdown is part of our standard package.
Related services
Related articles
Other articles that support the same decision
Technology Choice
Flutter or React Native? A Business-First Decision Guide
Let business goals decide, not hype. A 7-criterion 2026 comparison: performance, team fit, UI consistency, ecosystem, native bridge, maintenance cost, future security.
City Guide
Working With a Mobile App Team in Istanbul: Remote or Hybrid?
Istanbul's mobile ecosystem is large but dispersed. Remote, hybrid, or full office? A 6-criterion decision frame: traffic reality, rhythm, cost, control, culture.
Cost Analysis
Website Prices 2026: A Real Cost Guide
3 price bands, 8 cost lines, hidden lines, content + performance + SEO + maintenance. 8-heading data-driven website pricing guide.
Next step
If you are planning a similar project, we can clarify the scope and shape the right proposal flow together.
Start a project request