My developer and I have been working on this app for about 2 months. We have an MVP with no fancy bells and whistles. A part of me wants to delay the launch so that we can make it perfect but this is the OCD side of me speaking. Should I launch anyway and see what happens? Will launching an MVP be detrimental for us from a reviews standpoint?
This is my first app launch ever so I'm not sure what to expect.
Launch it without the bells and whistles. It is a MVP so it is suppose to be simple.
Your goal is to launch and test it with your market audience and see 1. If they are excited with your app. Not just friends, ask some strangers. I got about 100 testers for my MVP On TestFlight. Each market is different.
2. Great if they like the app and excited about it. How does this solve their current problem, what else do they need?
if not, what do you need to change? Why they don’t like it?
talk to them and do more research.
3. Feedbacks, feedbacks, feedbacks
With those data, back to building, launch and test again.
Don‘t wait! or you’ll never do it!! You may have lots of negative comments! True! But ir’ll make you only stronger! Unless you do it today you’ll never be able to really guess what they really want! Find it from the horse’s mouth and fix, fix, and fix. Until everyone is happy! Ubless you have a crystal ball That’s the only way You can find out what they really want!
Do you mean Apple App Store? In which case you might want to use TestFlight with some people who give you feedback.
I would just make sure that the user experience is not frustrating for users.
I mean, if the app works fine, even without "fancy bells and whistles" is still a working app!
If I was in your shoes, I would focus for one week or even less on user experience tests, gathering infos from your network (friends, followers, etc.) and, after that, if no relevant issues are faced, I would publish the app.
Nowadays releasing early MVP and testing your assumptions about the customer needs is a common approach.
I support all others here who tell you to release the app. If you're thinking it can give the app a bad name, just give it another name, relevant only in some area or market niche. For example if you're testing your MVP in Boston, give it a 'BostonApp' name...
Good luck! Never be afraid of receiving bad feedback. MVP is for learning, so as far as people tell you what they think - you fulfill MVP purpose.
First you must be clear about what you want/must learn next:
- How the release process work? Launch it
- If people are interested in your app? Launch a landing page and ask people to sign up to be notified when it is released. Pay attention to the bounce rate.
- If the app solves the problem it is set to solve? Find beta testers (you can find them on craigslist, facebook, linkedin or even starbucks) and use TestFlight (if it is an iOS app)
Remember this is all a big experiment and the key is to know what you want to learn next. You don't want to waste time releasing an app that nobody cares about, unless all you want to obtain from it is learning how to release apps.
One important caveat: people don't download apps anymore and those who do end up with a bunch of zombie apps on their devices, so keep that in mind to avoid disappointments.
What's your customer support plan for handling issues? Before launching anything, anywhere you need to address how issues complaints and bugs will be handled.
Nowadays people are looking for perfect and well tested app, so you should atleast have a working app with a good UI, error free (well tested whatever you have added till now in your app should be without bug and should not crash) to give user a well and good experience so they get back to you with their suggestions otherwise except developer and helpers everyone else will directly remove your app without wasting more time. So if you have atleast a basic perfect app then go ahead and get more share, likes and comment/suggestions from your users.
You also have an alternative which allows you to make your app perfect is you publish your app under development mode/early access mode which allows other developer/helpers to give you more valuable feedbacks to improve your app and then you can make it public.
If you're in doubt great way to gather early feedback is to release to closed group of beta testers. From technical point of view apart from iOS Test Flight there are also other options addressing both iOS and Android which can be pretty attractive before going public. Two popular ones are Fabric/Crashlytics (recently acquired by Google) and HockeyApp - both allow to manage test/closed release members group and also provide extra features like analytics, crash reporting etc. I am using Fabric for a few weeks now and I'm really happy with it so far - it allowed me to build continuous delivery workflow where release is done with just one command (and can be integrated into any CI/CD tool)
Personally, just my subjective evaluation..and how I purchase...I agree with those who have suggested testing within confined audiences. Nothing annoys me more than some poorly put together product or app. A lot depends on your definition of perfection. If its core use functions without error and serves a purpose, there is less to worry about. But if there are glitches in that function..me personally..not only will I trash it, I will never go back. Also, how much longer do you need to get it to where you believe is as close to perfect as you can get it? If you can afford that time, then why in the world would you launch now? Reckless abandon sounds great, but it is less realistic and practical to success than some on this post have inferred. If you know there are things you need to fix...fix them. If those things did not need to be addressed they would likely not be on your mind and far less important.