Blog / MVP · Product
What to build first: scoping an MVP that people actually keep
How to cut an app idea down to the version worth launching, what to include in a first release, and the features founders add too early.
· 2 min read · Vasoo
A minimum viable product is not a rough version of the whole idea. It is the smallest complete product that a user will keep. Getting the cut right is the difference between learning something in three months and running out of budget with nothing live.
Start from the retention moment
Ask what a user must experience in the first session to come back for a second. In a nail-design app it is seeing a design on your own hands. In a search app it is one result that felt impossible to find elsewhere. Build everything required to reach that moment quickly, and nothing else.
What belongs in version one
- ■Onboarding that reaches the retention moment in under a minute
- ■The core loop, complete with empty, error and offline states
- ■Account and data handling that meets store privacy rules
- ■A paywall or pricing test if the business model is subscription
- ■Analytics on the loop, crash reporting and a review prompt
What to defer
- ■Social features before there are users to be social with
- ■Admin dashboards that a spreadsheet can replace for now
- ■The second platform, unless both are genuinely required at launch
- ■Settings screens for preferences nobody has asked for
- ■Perfect localisation before the product is validated in one language
Write it down
A one-page scope with acceptance criteria is the most valuable document in the project. It lets a studio commit to a budget, lets you push back on scope creep, and gives everyone the same definition of done.
Our MVP app development engagements start with exactly this exercise. Start a project to book a Discover session.