By Alpit Patel and the aibrevo team · October 31, 2026 · 5 min read
What Is an MVP in App Development?
Quick answer
An MVP (minimum viable product) is the smallest working version of an app that real users can sign up for, use and pay for, built to learn whether the idea works before you build the rest. Eric Ries defined it as the version that collects the maximum amount of validated learning about customers with the least effort.
Key takeaways
- An MVP is a working product with real users, real data and, if you charge, real payments. It exists to answer one question: will people use this and pay for it?
- Eric Ries, who popularized the term, defined it in 2009 as the version of a new product that lets a team collect the maximum amount of validated learning about customers with the least effort.
- A proof of concept tests whether something can be built; a prototype tests whether users understand it; only an MVP tests real demand.
- Across the 44 builds in our published case studies, first versions shipped in 5 to 10 weeks with a median of 7; GoHangars shipped its marketplace MVP in 7 weeks from the first call.
- An MVP in the App Store still has to pass review. Apple's guideline 4.2 rejects apps that are not useful or are just a repackaged website, so minimum cannot mean empty.
An MVP (minimum viable product) is the smallest working version of an app that real users can sign up for, use and pay for. You build it to learn whether the idea works before you spend money on the rest. The core job works end to end; everything else waits until users ask for it.
Checked on October 31, 2026. The definition comes from Eric Ries’s original 2009 post. Build times come from the timeframe field of the 44 case studies on our work page, and store rules from Apple’s App Review Guidelines.
Source: our case studies, including GoHangars.
Where does the term MVP come from?
Eric Ries popularized it in the Lean Startup movement. In his post “Minimum Viable Product: a guide” (August 3, 2009), he defined the MVP as “that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort” (Startup Lessons Learned, checked Oct 31, 2026).
The key word is learning. An MVP is not a rough first draft or the version with the fewest features. It is the version that answers your biggest open question with real users, as fast as possible.
How is an MVP different from a prototype or a proof of concept?
| Proof of concept | Prototype | MVP | |
|---|---|---|---|
| Question it answers | Can this be built? | Do people understand it? | Will people use it and pay? |
| What it is | A technical test, often throwaway code | A clickable design, no real backend | Working software with real accounts, data and payments |
| Who sees it | The team | Test users | Real customers |
| Typical time | Days | 1 to 3 weeks | 5 to 10 weeks in our builds |
Many founders arrive at an MVP with a prototype already made. GoHangars’ founder came to us with a Figma file he liked and a 300-row spreadsheet of hangar operators. The design answered “do people get it”; the MVP had to answer “will owners book and pay”.
What should an MVP include?
Ask one question of every feature: does a user need it to get the core result the first time? If not, it goes on the after-launch list.
Usually in:
- Sign-up and login
- The core workflow, end to end
- Payments, if you charge
- A basic admin view, so your team can run the service
- Analytics, so you can see what users actually do
- Account deletion, which Apple requires for any app that lets people create an account (guideline 5.1.1(v))
Usually out:
- Social sharing, referrals and badges
- Multiple pricing tiers
- A second or third user type that is not essential on day one
- Custom animation and illustration
- Integrations that can be a manual step for the first hundred users
What does a real MVP look like?
GoHangars is a marketplace where aircraft owners find hangar space. We agreed a seven-week scope to a launchable marketplace with real listings, not a prototype. The MVP had separate onboarding for owners and operators, search by airport code with aircraft-fit filters, availability calendars and Stripe Connect payouts. Results from the case study:
| Measure | Result |
|---|---|
| Build time | 7 weeks from the first call |
| Aircraft owners registered | 480 within 90 days of launch |
| Hangar listings | 1,240 across 38 states in six months |
| Booking volume | $2.1M in year one |
A two-sided marketplace is about as complex as an MVP gets. Most MVPs are smaller: one user type and one core job, like the 6-week Stridely fitness app.
How long does an MVP take to build?
Across our 44 published builds, 5 to 10 weeks, with a median of 7 and 40 of the 44 at 8 weeks or less. Store steps come on top: Apple says 90% of submissions are reviewed in under 48 hours, and new personal Google Play accounts must run a 14-day closed test. The full breakdown is on how long it takes to build an app, and the money side on how much it costs to build an app.
Can a minimum viable product be too minimal?
Yes. If the core job does not work well, users leave and you learn nothing about demand, only about a broken product. For apps there is also a hard floor: Apple’s guideline 4.2 says an app should go beyond a repackaged website and be useful, unique or app-like, and Apple’s App Review page says incomplete submissions may be delayed or fail review (Apple, App Review, checked Oct 31, 2026). Viable means a real user would choose to use it.
What should you measure after launching an MVP?
- Activation. What share of sign-ups complete the core job once?
- Retention. How many come back after a week and a month?
- Willingness to pay. Do people pay, or ask to?
- Qualitative feedback. What do the most active users ask for?
Decide in advance what result means “keep going” and what means “change course”, so the data makes the decision.
If you have an idea and want it scoped to a first version, our MVP development team does that on a free 30-minute call. Before you share details, read how to protect your app idea, and check whether you need a backend for your MVP.
Sources
- Eric Ries, Minimum Viable Product: a guide, Aug 3, 2009, checked Oct 31, 2026.
- Apple, App Review Guidelines, sections 4.2 and 5.1.1(v), checked Oct 31, 2026.
- Apple, App Review, checked Oct 31, 2026.
- Clutch, App Development Pricing Guide, updated Sep 21, 2026, checked Oct 31, 2026.
- Our case studies: build timeframes for all 44 published builds on /work/, and GoHangars.