I think MVP's previously have been about shipping the quickest feasible product which accomplishes perhaps one core function. Is this still relevant?
I am not sure exactly how "simple" an MVP should be before its considered too simple. Are there any checklists I can go through?
I like to look at this framework when thinking about what an MVP should be like: https://brianpagan.net/wp-content/uploads/2015/08/MVP-brianpagan.net-diagram1.png
It should still be the quickest thing you can build (for the sake of the value of your own time and the total time that you have to iterate before the end of your runway). And I'd recommend you to think about what is the one core problem that you're solving for your customer and then build the minimal set of features to solve that problem. But at the same time it needs to have decent UX and look professional.
Don't put a lot of effort/money in "launching" until you have users that are willing to pay. Hand hold early users as much as possible.
This comment was deleted 8 years ago