Questions

We're launching our app soon http://teamstoryapp.com but we're wondering if we should do a closed beta or launch quietly... We know that launching in beta would give us good initial users and content creation (brand and community), but the downside of doing a beta is the friction for users to get on the application due to cumbersome process (TestFlight etc.) Some of us are afraid that people would churn because of this and suggesting launching the app quietly. Was anyone in the same situation? How do you go about doing this? Thanks in advance

I'd second what Dan said. Pick a small country, such as Canada, and do a quiet launch. Even if I get people to register their devices and join a beta distribution on TestFlight, it is still difficult to get real, workable feedback from them.

But if you launch in an App Store and make it very clear in your description and through in-app prompts that you're looking for feedback then you'll be able to iterate much faster. You'll also turn some of those early adopters into your most vocal advocates.

Once you've worked all of the kinks out of your MVP, and have validated your learning, a la Eric Ries, you can be confident that you've created something people really want.

One last thing: using the quiet launch as your beta will encourage you to ship this thing faster. The app ecosystem evolves so rapidly that I've come to believe that shipping an imperfect product is smarter than waiting for perfection. It's not until you hear from users that you know what perfection is anyway.

Hope this helps,
Austin


Answered 6 years ago

Unlock Startups Unlimited

Access 20,000+ Startup Experts, 650+ masterclass videos, 1,000+ in-depth guides, and all the software tools you need to launch and grow quickly.

Already a member? Sign in

Copyright © 2019 Startups.com LLC. All rights reserved.