What belongs in an MVP — and what can wait
A minimum viable product is not a cheap version of the full app. It is the smallest thing that lets real users get real value, so you can learn what to build next.
"Let's start with an MVP" is one of the most common sentences in app projects, and one of the most misunderstood. An MVP is not a lower-quality version of everything you have planned. It is a complete answer to one problem, for one group of people, done well.
Start from the job, not the feature list
Write down, in one sentence, what a user is trying to get done: "book a cleaner for Saturday morning" or "track a habit without thinking about it". Then list the steps that job truly requires. Those steps are your MVP. Everything else is a candidate for later.
What usually belongs in version one
- The core flow, from opening the app to the moment of value, with no dead ends.
- Sign-up and login, if users need to come back to their data.
- Basic error handling and empty states, so the app never looks broken.
- Analytics on the key steps, so you can see where people drop off.
- A simple way for users to send feedback.
What can almost always wait
- Social features, sharing and invitations.
- Extensive settings and personalisation.
- A second platform, if one clearly dominates your audience.
- Admin dashboards beyond the basics — a spreadsheet or a simple panel often works at first.
- Edge cases that affect a tiny share of users.
Minimum does not mean sloppy
The parts you do ship should feel finished. A short, polished flow builds trust; a long, half-working one destroys it. It is better to remove a feature entirely than to ship it at 60%.
Plan the learning, not just the launch
Before launch, decide what you want to find out and how you will measure it. "Do at least a third of new users complete their first booking?" is a question an MVP can answer. Without that question, you only have a smaller app — not an experiment.
The best MVP feature list is the one you feel slightly uncomfortable about. If it feels complete, it is probably too big.
After launch, let real usage — not the original wish list — decide what comes next. You will almost always be surprised by what people actually use.
