Will you release an MVP with bugs to validate the product idea?

Sayoni Dutta Roy
13 replies

Replies

RDS
I would say no because first impression is the last impression. Better make a small team or make some sort of beta program so, only selected people can test. This will even help you to not getting any -ve impact on a large scale.
@rds1 @edward_g Good point! How would you tradeoff perfection with the time taken to go to market?
RDS
@sayoni_dutta_roy As I have mentioned. Make a small team for beta testing. Once they start giving +ve review aka almost no major bug. You can release the app. Time taken depends on the developer that how much time he/she takes to fix the bugs
Edward G
No. Although its hard to get 100% of bugs ironed out, the major ones are most important. Why would someone waste their time with a second chance?
@edward_g Sure! But what if no one wanted the product in the first place (or nobody wanted what you thought they wanted) and the time you spent on making the product perfect was a wasted effort?
Edward G
@sayoni_dutta_roy Create a small POC first before creating the MVP to gauge interest. Start small and build gradually.
Peyt Spencer Dewar
Only if the bugs don't impede user experience. An MVP with bugs > no MVP.
anna_ch_anna
Even if there is a bug, I think it's a good attempt to release it first. However, it is better to reveal that it is a beta service. Since MVP is aimed at exploring customer demand, I think it would be better to release it first if only one key function is executed correctly.
@anna_choi Right! validate if anyone wants it first before making it perfect!
Mukesh Soni
Depends on the severity of the bugs. If it's not impacting the user experience then yes. Otherwise, a video of the product in action can also be be used. p.s. I recently posted a video of an MVP that I'm building here- https://www.producthunt.com/disc...