I can’t help myself to think that nowadays, products UX/UI level is so high, that even for B2B products, people have expectations.
I would certainly not use a product that looks and feels crappy even if it solves my needs.
I could possibly don’t see how it solves my needs if it does it in a crappy way too.
What are your thoughts?
No.
Why not just start with the landing page and nail the value prop (MVP). Build a beta and get feedback. Then build and launch a V1.
A while back I wrote this MVPs Types list. Probably it might help others https://www.reddit.com/r/SideProject/s/C4TEaS4eXT
For most of the use cases, future is API economy with AI. So if we push B2C solutions to where customers are already like X, Insta, FB, WA. We should service customers where it adds more value. My 2 cents, maybe it doesn’t apply to all. It has to be way apple changed how we used Telephone in 1942.
Having said, what it WA, X goes bankrupt in 5-10 years like Nokia, as blockchain, VR world is next Gen future.
For my personal use I feel the opposite. (Although I’m definitely not the demographic you should target)
I prefer simple and sometimes less intuitive UIs since they usually indicate the product is either function-oriented or from a small team. When things are too polished it feels off putting and sterile. I’d use Windows Vista over MacOS any day.
But to answer your question, no I don’t think MVPs are dead. Instead of doing 100% of your product’s features at 50% quality, you should focus on doing 50% of your final product at 100% quality.
The idea is still to make something that’s just good enough to bear its own weight and demonstrate the concept to potential investors. The only thing that’s changed is what people are expecting
MVP to me seems more like the mentality of okham’s razoring any ancillary features that are not core to your product’s viability. If a good UX/UI are critical to your product’s viability, then it is part of the MVP.
My friend Chris calls these “birthing rights.”
For some products and MVP could be very crappy and you would still use it because it’s novel and solves a problem in an unexpected way, or does something new where trying the product is worth the experience.
For the rest of the products you have expectations of what they look like and how they work, and if those features are missing, then indeed you will not even consider trying.
I think this has been the case for a very long time, but now that coding is becoming somewhat obsolete, simple MVPs are dying indeed. No one needs another X for Y. Your product has to be wildly different to still be accepted as an MVP.
Maybe the word you want here is “prototype” and not MVP? Since MVP is still an actual product, tho not filled to the brim with features. Prototype however is more of a proof of concept thing. Doesn’t need fancy ui/ux.