10
9 Comments

Prototype vs MVP

  1. 3

    Very well articulated.

    One thing I would note is that more often than not, prototypes end up becoming MVPs, and that bad code/UX tends to live on much more than we'd like to admit. So just be careful with prototypes, because it's easy to get stuck with that foundation forever!

    1. 2

      Oh god - absolutely! This is actually the main reason that I'm so pedantic / wary of the whole "MVP" thing. See my reply to @rab above.

      If I had £1 for every time I've been told "just get it out the door quickly and we'll go back and fix it up later" and then that NEVER happening - I'd already be a wealthy guy.

  2. 1

    totally agree with all written here. what worries me is this new scary world of no/low code usage to build MVP's.

    I'm old school (first used computer in 1983) and have a bit of a problem with these new tools, but appreciate the world might go that way. But the worry is how to take some low-code MVP solution built on a platform that has basically tied the startup in. It seems so difficult to convince these startups that they are wasting a lot of money, because the whole thing needs scrapping and starting again "in real code".

  3. 1

    If you swallow Lean Startup then MVP is:

    a version of a new product that allows maximum validated learning about customers with least effort.

    Choose easy solutions (first-cut, less than ideal, low-cost), build "tent-pole features for early adopters" and incur "technical debt".

    Implies elements will be replaced, meaning they don't have to be high-quality nor maintainable.

    Because MVP is so nebulous there are a lot of different interpretations. MVP could probably do with a better name.

    "Validating Value Proposition" is possibly closer to what Robinson / Ries / Blank meant ("Manufacturing Value Proposition" if you want to stick with MVP - but it's a bit ugly).

    1. 1

      Agree to a certain extent - the context here is when you're in a team or a company where its usually (almost always) not the case where dev teams have the liberty to go back and re-do things.

  4. 1

    A nice reminder as I am working on my second product. The first, I went overboard with features. For this new project, I am focusing on M V P. Only the bare bones of what I need to launch.

    1. 1

      How are you choosing which features to include?

      1. 2

        Well I actually received a lot of feedback initially, so i'm including only those in which people were interested in.

        Much better than my first project, ignoring feedback and what people actually wanted.

  5. 1

    I agree with you, I think a "prototype" is something that can look like shit as long as your, well, prototyping. An MVP is something that you can put your name behind and sell. In my eyes, you don't sell a prototype - you pitch it and then make it better.

Trending on Indie Hackers
Share your product if you haven't made your first sale :) 103 comments I redesigned my landing page to something completely unconventional/unprofessional 32 comments How we automatically provision SSL for SaaS customers with custom domains 14 comments On productized services, a crappy logo, and a shift in perspective that changed everything: Jaclyn Schiff's story 10 comments New vlog: Bought my dream car after 10 years of hard work in entrepreneurship! 7 comments $7000 in 7 days with an e-book. Channels breakdown. 3 comments