Android App Development · Minimum Viable Product

How much bugginess would consumers tolerate in version 1.0 of an App?

Roman Tsukerman Go big or go home

September 14th, 2016

I'm in pre-Beta of an Android app and we're seeing little issues like current GPS address not loading for 5+ minutes, the app crashes during a page-flip animation about 15% of the time, the "refresh" button animates nicely but does nothing, and 2 of the 4 core features work only 80% of the time. How finished should the app be before I show it to investors? How reliably should it operate before I can label it MVP and release? Thanks!
You have an idea. Now it’s time to turn it into a brilliant and beautiful product. In this course, you’ll learn specialized tactics to study your user, create testable wireframes, and transform them into fully functioning features and products.

Anthony Miller

September 14th, 2016

Do you have anyone who has signed up for the product launch? It sounds like those bugs could cause some user abandonment. If you've solved a problem in the marketplace and have demonstrated good revenue models you can approach investors but it sounds like (And if I'm wrong let me know) that you don't have any traction. Maybe still too early. Keep iterating and get some traction.

Ken Vermeille Founder

September 14th, 2016

Hey Roman, it all really comes down to 1 thing. Despite all of the bugs, does your app solve a user's problem relieves their pains and creates unexpected gains? If so then most early adopters are very lenient when it comes to things like this. I do suggest that you put in a bit more development time because you don't want all your beta testing impressions to be marred by these bugs. From what you say however, it seems like the bugs break the entire experience. Stop the beta, take stock of what you need to fix, and put out a solid working version. Also do a feature freeze. No new features until the bugs are fixed!