Read from Apple’s and Google’s own rules
What is an MVP? A minimum viable product, and why an app’s first version still has to be finished
MVP stands for minimum viable product: the smallest version of a product that lets you start learning from real people. In start-ups, “minimum” can mean very little. An app is different. Before the public can download it from the App Store or Google Play, it has to meet Apple’s and Google’s rules, and both turn away apps that don’t do enough or don’t work. Here’s what MVP means, what the two stores accept from a first version, in their own words, and what to ask a developer who suggests starting with one.
The short version
- An MVP is a minimum viable product. The smallest version of an idea that real people can use, so you learn what they actually want before you build the rest.
- For an app, “minimum” has a floor. Apple has a rule called “Minimum Functionality”. Google Play says “We do not allow apps that only have limited functionality and content.”
- Demos and betas don’t go in the store. Apple: “Demos, betas, and trial versions of your app don’t belong on the App Store – use TestFlight instead.”
- The learning can start before the store. Apple’s TestFlight takes up to 10,000 outside testers; Google Play has internal, closed and open tests.
- Some Google Play accounts must test first. A personal account created after 13 November 2023 needs a closed test with at least 12 testers for 14 days before the app can go public.
- So an app MVP is small, but finished. One job, done properly, tested by real people.
What does MVP mean?
MVP stands for minimum viable product. The Lean Startup method’s own site puts it like this: “The first step is figuring out the problem that needs to be solved and then developing a minimum viable product (MVP) to begin the process of learning as quickly as possible.”
The point is learning, not saving money. The same page says it plainly: “Lean isn't simply about spending less money.” An MVP is the least you can build that still tells you something true about what people want, because they’ve used it, not because they’ve said so in a survey.
That matters for apps more than most things. People rarely know what they want from an app until they’re holding one. A first version in their hands answers questions a long specification never will.
What is an MVP in app development?
The same idea, with one difference. To learn from people using your app, they have to install it, and for most people that means the App Store or Google Play. Both stores have rules an app must meet before the public can download it, and Apple reviews every app submitted. So the “minimum” in an app MVP isn’t only yours to decide. Apple and Google set a floor.
What the App Store accepts
Apple’s App Review Guidelines are the rules every App Store app is checked against. Three of them bear directly on a first version.
It has to be complete. Guideline 2.1 is called “App Completeness”: “Submissions to App Review, including apps you make available for pre-order, should be final versions with all necessary metadata and fully functional URLs included; placeholder text, empty websites, and other temporary content should be scrubbed before submission.” It goes on: “Make sure your app has been tested on-device for bugs and stability before you submit it”, and, if the app has a sign-in, include a demo account “(and turn on your back-end service!)”.
It can’t be a demo. Guideline 2.2: “Demos, betas, and trial versions of your app don’t belong on the App Store – use TestFlight instead.”
It has to do enough. Guideline 4.2 is literally called “Minimum Functionality”: “Your app should include features, content, and UI that elevate it beyond a repackaged website.” And: “If your App doesn’t provide some sort of lasting entertainment value or adequate utility, it may not be accepted.” Next to it, 4.2.2 says apps “shouldn’t primarily be marketing materials, advertisements, web clippings, content aggregators, or a collection of links.” If your MVP plan is your website inside an app, we covered why that runs into these rules in turning your website into an app.
What Google Play accepts
Google Play’s policy on functionality, content and user experience sums itself up in one line: “Apps must be stable, functional and provide meaningful content.” Then, under “Limited functionality and content”: “We do not allow apps that only have limited functionality and content.” Its examples of what breaks the rule include:
- “Apps that are static without app-specific functionalities, for example, text-only or PDF file apps”
- “Apps that are designed to do nothing or have no function”
And under “Broken functionality”: “We don’t allow apps that crash, force close, freeze or otherwise function abnormally.” Google’s own advice in the same policy: “Don't publish apps that have very little user functionality.”
Neither store counts features. A small app that does one useful thing well isn’t what these rules are aimed at. A half-built one is.
Where an app MVP gets tested first
Here’s the good news for anyone who wants to learn early. Both stores have a way to put a real app in real people’s hands before it’s public, and that’s where much of the learning in “minimum viable product” can happen.
| Store | How testers get the app | How many |
|---|---|---|
| Apple | TestFlight, people on your own team | Up to 100 |
| Apple | TestFlight, outside testers, by email invitation or a public link | Up to 10,000 |
| Google Play | Internal test | Up to 100 |
| Google Play | Closed test, people you choose | Google’s page says “a wider set of testers” |
| Google Play | Open test, visible on Google Play | “Anyone can join an open testing programme” |
From Apple’s TestFlight page and Google’s page on test tracks.
Testing isn’t a way round the rules, though. Apple’s TestFlight page says that to invite outside testers you need your “first build already approved by App Review for TestFlight”, and guideline 2.2 adds: “Any app submitted for beta distribution via TestFlight should be intended for public distribution and should comply with the App Review Guidelines.” A test build is checked too, just earlier.
New personal Google Play accounts must test first
One more rule applies to some accounts. Google’s testing requirements say: “Developers with personal accounts created after November 13, 2023, must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days.” Only then can you apply to publish, and the application asks about your test, including “Whether testers used all available app features”.
So on a new personal account, an app can’t go straight on to Google Play: there are at least two weeks of testing with at least 12 people first. Google’s article is about personal accounts only, and says nothing about accounts set up for a business. Which name an app goes out under matters for other reasons too; setting a business account up needs a DUNS number, which you can get free.
So what does an app MVP look like?
Putting the two stores’ rules together, this is our reading of what a first version needs:
- One job, done properly. If it’s a booking app, booking, changing and cancelling work end to end. Loyalty points, chat and the rest can wait.
- Real content. Apple’s word is “scrubbed”: no placeholder text, no empty pages.
- Everything it needs actually working. Sign-in, payments if it takes them, and whatever it connects to behind the scenes.
- Something a website can’t do as well. Otherwise Apple’s 4.2 applies.
- Tested by real people before it’s public. TestFlight and Google Play’s test tracks are where you learn what to change next.
Small in scope, not in finish. That’s the difference between an app MVP and a demo.
What to ask a developer who suggests an MVP
“Let’s start with an MVP” is often good advice. These questions make sure you and your developer mean the same thing:
- What’s the one job this first version does? If the answer is a list, it isn’t minimum yet.
- Is it meant for the stores, or only for testing? Both are fine. But a build for the App Store or Google Play has to pass their checks as it is.
- Who will test it, how, and for how long? TestFlight, a closed test on Google Play, or both. On a new personal Google Play account, plan for 12 testers and 14 days.
- Whose Apple and Google accounts does it go out under? Yours, ideally. We explain why in what to check before you hire an app developer.
- What happens after people have used it? An MVP is only worth it if what testers do changes what gets built next. Ask how changes are made, and how often.
What argues the other way
- Not every MVP has to be an app. If the question is “will anyone want this?”, a web page, a form or doing the job by hand for a few customers may answer it faster than any app. That’s our view, not the Lean Startup site’s.
- The rules are written broadly. Apple’s “adequate utility” and Google’s “meaningful content” are judgements made by reviewers, and neither store’s pages say how strictly they’re applied. We’ve reported what the rules say, not how often they’re enforced.
- Our interest. We build apps for UK businesses, so a post saying a first version has to be finished suits us. Everything quoted here is from Apple’s and Google’s public pages, and any developer can read them.
Sources, and what we checked
- Apple: the App Review Guidelines (the page says “Last Updated: October 16, 2026”), guidelines 2.1, 2.2, 4.2 and 4.2.2; and the TestFlight page, which guideline 2.2 links to.
- Google Play Console Help: the policy “Functionality, content and user experience”; “Set up an open, closed or internal test”; and “App testing requirements for new personal developer accounts”, which that page links to. Google showed the last one to us in American English, so its quotes keep “November 13, 2023”.
- The Lean Startup: the principles page on the site of The Lean Startup, Eric Ries’s book. We haven’t read the book itself, so we don’t quote its definition or say who first used the term.
- We keep each source’s own punctuation inside quotes, including Google’s and the Lean Startup site’s straight apostrophes.
- All of the pages above were read in full on 7 November 2026, and again on 9 November 2026, the morning we published. Every quotation was checked word for word against the page it comes from.