Back to Digital Diaries
App Development5 min readNovember 2026

What to Include in an MVP (and What to Leave Out)

What to Include in an MVP (and What to Leave Out)

Most first-time founders arrive with a feature list that would take a year to build. The list isn't wrong, exactly. Every item on it is something a real customer might want eventually. The problem is that an MVP isn't a smaller version of the finished product. It's an experiment, and an experiment needs a question before it needs features.

The question is usually some version of this: will a specific group of people use this to solve a specific problem, and will they pay for it? Everything in the first build should help answer that. Anything that doesn't can wait.

Start With the One Job

Write down, in one sentence, the job a user hires your product to do. "Book a cleaner for tomorrow morning." "Send an invoice and get paid by card." "See which of my stores is short on stock."

Then map the shortest path from a new user opening the app to that job being done. That path is your MVP. On most products it's somewhere between four and eight screens.

If you can't write the sentence, the build isn't the next step. Talk to ten potential users first. It costs nothing and it will change your feature list more than any amount of planning.

What Belongs in the First Build

  • The core flow, done properly. The path from sign-up to the job being done should feel finished. This is the part users judge you on, so it gets the design attention.
  • Accounts and authentication. Email and one social login is plenty. Use an established service rather than building your own.
  • Payments, if you're testing willingness to pay. A working Stripe checkout tells you more than a hundred survey responses saying "I'd pay for that."
  • Basic analytics. You need to see where people drop off. Without it you'll be guessing about why the numbers look the way they do.
  • A way to reach you. A support email or a chat widget. Early users who get stuck and can reach a human become your best source of feedback.

What Can Wait

  • An admin dashboard. For the first few hundred users, you can manage data directly in the database or through a tool like Retool. A custom admin panel is a real project in itself.
  • Both iOS and Android, if you're building native. Pick the platform your target users are on. If you genuinely need both, a cross-platform framework like React Native or Flutter gets you there from one codebase.
  • Notifications beyond the essential. One transactional email (a receipt, a confirmation) is enough. Digest emails, push campaigns and in-app messaging come later.
  • Settings and preferences. Choose sensible defaults and leave out the settings screen. Add options when users ask for them.
  • Roles, teams and permissions. Unless the product is fundamentally about teams, a single user type will carry you through validation.
  • Integrations. Each one is a dependency you'll have to maintain. Add them when a paying customer needs one.

The "Just One More Feature" Trap

The most common reason MVPs run late is that features get added after the build has started. Each one seems small, but each also touches design, testing and the features around it.

A useful rule: anything new that comes up during the build goes on a list for version two. When the MVP ships and real people are using it, revisit the list. Usually half of it no longer seems important, and a few things nobody thought of have taken its place.

Build to Learn, Then Build to Last

Keeping the scope small isn't the same as cutting corners. The code under an MVP should still be clean enough to build on, because if the experiment works, you'll be extending it rather than throwing it away. What you're cutting is breadth, not quality.

If you have an idea and want help working out which parts belong in the first version, that conversation is the first stage of our MVP process. You can also get in touch with what you have so far, even if it's only a rough outline.

Need help implementing this?

We wrote about it. We can also build it for you.

Get in Touch WhatsApp