An MVP, minimum viable product, is the smallest version of your app that still solves one real problem for one real user. It’s not a prototype and it’s not a mockup. It’s a working product, just with fewer features than the app in your head.

MVP, defined properly

A prototype looks like an app but doesn’t really work. A mockup is a set of static screens. An MVP is neither, it’s live, functional software that does one thing properly. The difference matters because only an MVP can actually be used, tested, and learned from.

Why most first apps fail, and it’s rarely the idea

Most failed app projects didn’t fail because the idea was bad. They failed because the first version tried to do everything at once, took months longer than planned, cost far more than budgeted, and launched to silence because nobody had tested the core idea along the way.

What belongs in an MVP, and what doesn’t

  • In: the one workflow your app absolutely must get right
  • In: enough screens to complete that workflow start to finish
  • Out: every feature you can imagine your app eventually having
  • Out: admin dashboards, multiple user roles, and marketplace features, for now
  • Out: pixel-perfect polish on parts of the app people barely use

A real example

Our beauty and wellness concept, Studio, is a good illustration. A full salon platform could include staff rotas, marketing tools, loyalty points and inventory. The MVP version does one thing: let a client see availability and book an appointment. Everything else can wait until real bookings prove the idea works.