No items found.

More info

A common objection to building an MVP, or Minimum Viable Product, is that it could end up being a rushed, shoddy product with a messy code base. But people forget this is not a proof of concept we're building here. This is a functioning, early version of your product that will end up in the hands of customers.

You can’t validate your hypothesis if your MVP doesn’t do what it’s supposed to do. So that already implies whatever features your app or website required at the time, have to work properly.

But whether the code you're writing is nice and tidy, is a different thing altogether. It depends on who you're asking, but in general, engineers will mention stuff like:

👉 Code has to be well-organized and readable.

👉 Code has to be fully tested and optimized.

👉 Code needs to have full error handling.

That's partially correct, in my opinion. Keep in mind what an MVP is really for. Are you going to pay an engineer to spend hours optimizing and refactoring code for a product you're not even entirely sure people will love?

Don't miss out

Sign up for our monthly newsletter to get the latest insights delivered right to your mailbox!
By clicking subscribe you agree to our terms and conditions
Thank you for subscribing to our newsletter!
Oops! Something went wrong while submitting the form.