[ramadis]

I think the whole point of an MVP is to validate the hypotesis you make about your users.

In your case for example, do you know who your users are? Are they entrepreneurs? Current software developers? Anyhow, who is going to use your service?

I'm not trying here to undermine your project since it indeed sounds pretty awesome, but to reinstate why the whole mvp movement has a reason to be.

[daliwali]

For marketing-tech, sure it's a great model, but getting out an MVP as fast as possible doesn't always make sense. Sometimes it takes an order of magnitude more effort to get to "minimum" or "viable" depending on the product. On the contrary, a lot of developer's side projects just feel like things that any reasonably skilled developer could build given a few days.

The question of finding customers, is exactly the same as finding who is demanding software to solve business problems (i.e. not current software devs).

[aregsarkissian]

Getting an MVP out as fast as possible doesn't contradict an MVP that takes an order of magnitude more effort to build. It's just that the ASAP for the latter case is whatever amount of time that it takes to build it.

[ramadis]

I agree with you about the complexity of a mvp. It indeed may vary. However a mvp is about testing an hypothesis, not building a simple version of a product.

Maybe an mvp for a complex product is just a landing page explaining features with a buy button, built in under 2 hours using optimizely.

Again, it depends on the hypothesis. So, in this way, I differ with you when you say getting out a mvp asap doesn't make sense. Because validating you hypothesis is what you want to make as fast as possible. But then, launching as fast as possible doesn't imply necessarily launching fast.