Hey guys,<p>I've been Googling for articles that talk about rolling out with a beta phase and I haven't found many. What apps should you release with a beta phase first, or should you release all apps with one? In what cases would you not want to have a beta phase? Doesn't a beta phase hurt the chances of an app going viral?<p>I thought these questions would be perfect for the HN community.<p>Happy holidays!
Beta phase for an existing app (new version) or completely new app? I'm not sure it matters much if you slap a 'beta' label on a new app. When you first kick an app off, you're going to be closely monitoring crash reports, bug reports, reviews, feedback, etc regardless of if you call it 'beat' or not.<p>A 'beta' label is not going to stop or cause your app to go viral. If your app does take off but crashes and is full of bugs, 'beta' is not going to stop negative reviews.<p>If you are concerned about bugs or need more testing, try out Fiverr or any of the mobile testing startups.
Hi, i never thought much about it, because in my view the beta phase is just there to get many feedbacks on the product itself. This might be usability, bugs or even more fundamental feedbacks.<p>But like you mentioned, it also might be a good chance for promotion ... if you want to promote an unfinished product ... depends on the basic "revolutionary" idea you are trying to spread.
People don't care what a beta is, they care if it works or now. Be careful if you list your app in a place where people can review it. People view things for what the are, not for what the can be.