Loading...
Answers
MenuiOS App: Beta vs Launch Quietly?
Answers
I would suggest launching in a foreign app store only (ex: Canada). That will allow you to get more organic users to continue iterating without a big push.
I got this idea from Matt Brezina (Founder of Sincerely, previously Xobni) https://clarity.fm/brezina - he's the man when it comes to testing & iterating mobile apps.
I think deliberating private beta ends up with a lot of wasted effort. It's far better to recruit your initial user panel and learn a ton there especially with something like TeamStory that is essentially expecting to successfully establish a new behaviour amongst its users.
I think Dan and Austin's advice is right for a lot of apps but not for something like TeamStory
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
I'm of the opinion of launching as soon as you can. You can only really learn when the app hits the wild. Realize though that apps are not websites, they can't be iterated as fast and a furry of bad reviews because of a buggy launch can haunt you forever. Some initial closed, pre-App Store launch is needed to make sure the basics are covered. No crashes, no major UX bottlenecks and ease of performing the 2-3 main things you want people to do.
Dan's idea is great if you'd like to save the US (or any other country of your choice ) for a big launch with press and a furry of users. Then you'd want some things further iron out. Some apps never do this and just organically grow their way to awareness by pure awesomeness and hustle.
Btw, love the idea and just signed up for the beta ;)
If your app is based on large numbers and collaboration/team, I'd go with public launch. Betas are good for initial feedback (almost pre-MVP) or for apps that target power users.
However, no one is stopping you from doing both if you have doubts.
Related Questions
-
Any opinions on raising money on Indiegogo for an app?
Apps are difficult to fund on IndieGoGo as few are successful, and we rarely take them on as clients. Websites like http://appsfunder.com/ are made for that very reason, but again, difficult to build enough of a following willing to pay top dollar for an app that could very well be free, already existing in the marketplace. A site that is gaining more traction you may want to look into would be http://appsplit.com/. Again, Appsplit Is Crowdfunding For Apps specifically.RM
-
Pre-seed / seed funding for a community app... valuation and how much to take from investors?
To answer your questions: 1) Mobile companies at your stage usually raise angel funding at a valuation equivalent of $5,000,000 for US based companies and $4,000,000 to $4,500,000 for Canadian companies. 2) The valuation is a function of how much you raise against that valuation. For instance, selling $50,000 at $5,000,000 means you are selling debt that will convert into shares equal to roughly 1% of your company. 3) I would encourage you to check out my other answers that I've recently written that talk in detail about what to raise and when to raise. Given that you've now launched and your launch is "quiet", most seed investors are going to want to see substantial traction before investing. It's best for you to raise this money on a convertible note instead of actually selling equity, especially if you are intending on raising $50,000 - $100,000. Happy to schedule a call with you to provide more specifics and encourage you to read through the answers I've provided re fundraising advice to early-stage companies as well.TW
-
I've been working on an app concept for 6 months and built an MVP. Is it better to pay a development firm to build or hire a developer as a cofounder?
I have built two software companies by hiring out the development work. I sold one for a decent sum during the dot com era (circa 1999). I remain a shareholder in the other one. I currently work with amazing development company on behalf of one of my clients. Here are some things to consider. 1. Do you really want to give up equity? If not outsource. 2. How fast do you want to get to market? If sooner than later, outsource. 3. How capitalized are you? If undercapitalized, either outsource offshore (which runs about 20% of US rates), or bring on an equity development partner. I offer a free call to first time clients. Let's chat and I'll give you some great advice from three decades of experience. Just use this link to schedule the free call: https://clarity.fm/kevinmccarthy/FreeConsult Best regards, Kevin McCarthy Www.kevinmccarthy.comKM
-
What is the best technology for developing a new mobile app from scratch?
There are two sides to that question. One is the mobile app itself and the other is the backend. If I misunderstood in any way and you didn't mean "native" app I apologize in advance. On the backend, there is no clear cut answer to which is the "best". It depends solely on the developers you are able to get. We for example use Node.js , mongoDB, redis, elasticsearch and a couple of proprietary tools in the backend. But you have your pick of the litter now both on the backend api and the datastore with the myriad of options available and touted as the "best" currently on the market. Now on the app side again it solely depends on what you need your mobile app to do. Experiencing first-hand "develop once, run anywhere" I can say it's more like "develop once, debug everywhere" to quote a Java saying. We have tried Phonegap and Titanium Appcelerator and we have switched to native (ObjC and Java) after a couple of months of trying to go the hybrid route. The reasons behind the choice are as follows: - anything that breaks the pattern of how those frameworks NEED to operate is just a huge technical debt that keeps accruing a huge interest. - anything that uses css3 accelerated animations on Android is buggy at best and slow as hell at worst on any lower (< 4.1 I think) versions of Android I hope this gives you some insight. If you need/want to ask me anything feel free to contact me. MihaiMP
-
Where can I find programmers willing to join a growing mobile start up for equity only?
You won't find anyone worth adding to your team willing to work for equity only, no matter how compelling your product and business is. The realities of the talent market for mobile developers anywhere is such that a developer would be foolish to work only for equity unless they are a cofounder and have double digit equity. Happy to talk about hiring and alternatives to full-time hires.TW
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.