Hi all, I'm assessing the pros/cons of different approaches to Beta- testing an app before it's ready for prime time.
Let's say I launch an app with a "BETA" label - purpose is to gain user feedback and make significant improvements before launching it "for real." (I don't know any other way to release as Beta except to test outside of the Android Market, on other app sites (slideme.org , mall.soc.io/ apps, etc) or private Beta.) **What is the 'relationship' in the App Store between the BETA version and the (post-beta) RELEASE Version?** Specifically 1. Will my app's user reviews be averaged starting with, and *always* including BETA reviews, OR is the Release Version a fresh start, with 0 reviews? (I'd prefer not having my review averages dragged down by poor reviews of the Beta Version.) 2. Is there any Android Market policy, or other foreseeable backlash, if we: 2a. Make the Beta free, but charge money for the Release Version? 2b. Make the Beta free, and then launch a free Release Version with some of the Beta-tested features (then-free) turned into PAID features? (Could be achieved either by in-app purchase, or by offering both Lite/Free and Paid/Full versions) Any references to Android Policy and/or your experiences would be greatly appreciated. Thanks everybody. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
