Building a new app
MVP App Development: How to Scope, Build and Launch a Minimum Viable Product
Short answer: An MVP is the smallest version of your app that delivers the core value to real users and lets you learn whether they want it. Scope it around one core loop. Include only what's needed for a user to get that value and for you to measure it: auth, the core feature, payments if you're testing willingness to pay, and analytics. Use mainstream, cross-platform tech so the MVP can grow instead of being thrown away. Most focused MVPs take 6–12 weeks.
What is an MVP, and what isn't it?
An MVP is:
- A real, working product that solves one problem well
- Built for a specific group of early users
- Instrumented so you learn from usage
An MVP is not:
- A buggy prototype you're embarrassed to show
- Every feature at 50% quality
- A throwaway. A good MVP is the foundation of version 2.
I'd rather ship four features that work beautifully than twelve that half-work.
How do I decide what goes into the MVP?
Use three buckets:
Must have: without it, the core loop doesn't work or you can't learn Should have: improves the experience but the loop works without it Later: everything else
Then be ruthless: move half the "should haves" to "later."
Common must-haves
- Sign-up and login (Sign in with Apple/Google to reduce friction)
- The core feature, done well
- Onboarding that gets users to value quickly
- Payments, if paying is part of what you're testing
- Analytics and crash reporting
- Account deletion and privacy basics (required by the stores)
Common "later" features
- Social feeds, messaging, comments
- Admin dashboards (use your database tools at first)
- Web version alongside mobile
- Deep settings and customisation
- Multiple user roles
- Integrations that only a few users asked for
What does a typical MVP timeline look like?
| Phase | Duration |
|---|---|
| Discovery and spec | 1–2 weeks |
| Design (overlapping with build) | 1–3 weeks |
| Core build | 4–8 weeks |
| Beta testing | 1–2 weeks |
| Store submission | Days to 2 weeks |
My fastest app, Drip, went from idea to the App Store in three days because the scope was one sentence long. Most MVPs aren't that small, but the principle holds: smaller scope means faster learning. (App timelines)
Which tech choices keep an MVP flexible?
- Cross-platform mobile (React Native + Expo): iOS and Android from one codebase, plus over-the-air updates for quick fixes
- Managed backend (Firebase or Supabase): no servers to run, scales with you
- Proven services for payments (Stripe, RevenueCat), email and push
- TypeScript and a clean structure, so version 2 builds on version 1 instead of replacing it
See native vs. cross-platform and the stack I recommend.
What should I measure after launch?
Define success before launch:
- Activation: % of new users who complete the core action
- Retention: day 1, 7 and 30, by cohort
- Conversion: % who pay, if you're charging
- Qualitative: user interviews and reviews. What do people love? What confuses them?
Then decide: double down (strong retention), iterate (activation or retention leaks you can fix), or pivot (people don't come back no matter what).
What MVP mistakes should I avoid?
- Scope creep during the build. Keep a "v2 list" and add to it instead of the current sprint.
- Skipping analytics. You'll launch and have no idea what happened.
- Over-engineering for scale. You don't need infrastructure for a million users before you have a hundred.
- Under-engineering the basics. Broken login or payments kill trust instantly.
- No budget after launch. Plan for at least 2–3 months of iteration.
FAQ
How much does an MVP app cost?
A focused MVP from an experienced independent developer typically costs $20,000–$60,000, depending on features, platforms and integrations. See app development costs.
Should my MVP be on iOS, Android, or both?
With React Native, both is usually only 10–20% more work than one. If your users are mostly on one platform, you can launch there first.
Can an MVP be built with no-code tools?
For testing demand, yes. For a product you plan to scale, especially with payments and complex logic, code is usually the better long-term foundation.
What happens after the MVP?
You measure, talk to users, and iterate. Fix activation and retention leaks before adding features. Budget for ongoing development and maintenance.