1page.title=Get real user feedback with beta tests 2page.metaDescription=Run alpha and beta tests from the developer console, and make improvements and correct issues before you release. 3page.image=images/cards/distribute/engage/beta.jpg 4page.tags="beta, alpha, release channels" 5Xnonavpage=true 6 7@jd:body 8 9<p> 10 With alpha or beta tests run from the Developer Console you can collect user 11 feedback on early versions of your app, then make improvements and correct 12 issues before you release to the full Play Store audience. 13</p> 14 15<img src="{@docRoot}images/distribute/googleplay/dev-console_running-a-beta-test.png" 16 srcset="{@docRoot}images/distribute/googleplay/dev-console_running-a-beta-test.png 1x, 17 {@docRoot}images/distribute/googleplay/dev-console_running-a-beta-test_2x.png 2x" 18 width="500"> 19 20<p>Testing your app with a select group of users will give you a chance to fix any technical or user experience issues before you release it widely, so that you can be confident about releasing the best version of your app to the majority of your users. Feedback from your test users won't affect your app’s public rating.</p> 21 22<p> 23 Learn more about <a href= 24 "https://support.google.com/googleplay/android-developer/answer/3131213" 25 class="external-link">how to run a beta test.</a> 26</p> 27 28<h2 id="how-to">How to Do It</h2> 29 30<ul> 31 32<ul> 33 <li> 34 <strong>Open beta —</strong> Use an open beta when you want any user who 35 has the link to be able to join your beta with just one click. One of the 36 advantages of an open beta is that it allows you to scale to a large number 37 of testers. However, you can also limit the maximum number of users who can 38 join. 39 </li> 40 41 <li> 42 <strong>Closed beta using email addresses —</strong> If you want to 43 restrict which users can access your beta, you have a new option: you can 44 now set up a closed beta using lists of individual email addresses which 45 you can add individually or upload as a .csv file. These users will be able 46 to join your beta via a one-click opt-in link. 47 </li> 48 49 <li> 50 <strong>Closed beta with Google+ community or Google Group —</strong> You 51 can continue to use betas with Google+ communities or Google Groups. You 52 can also move closed betas to an open beta while maintaining your existing 53 testers. 54 </li> 55</ul> 56 57<h2 id="tips">Tips</h2> 58 59<ul> 60 <li>Your testers will need to have a Google Account (<code>@gmail.com</code>) 61 or a Google Apps account to join a test. 62 </li> 63 64 <li>Use alpha tests for early experimental versions of your app that might 65 contain incomplete or unstable functionality, and use beta tests for apps 66 that should be complete and stable. 67 </li> 68 69 <li>Start testing with a small group of more trusted testers in an alpha 70 test, then expand your test to a larger group of testers in a beta test. 71 </li> 72 73 <li>Testers can't leave public reviews for alpha/beta apps on Google Play, so 74 include a feedback channel or provide the option to send feedback by email, 75 website, or a message forum. 76 </li> 77 78 <li>For an APK to be available to alpha testers it must have a higher version 79 number than your beta or production version, and for beta testers the APK 80 must have a higher version number than your production version. 81 </li> 82 83 <li>Alpha testers receive the alpha, beta, or production version of your app 84 with the highest version code that is compatible with their device, while 85 beta testers receive the beta or production version of your app with the 86 highest version code that is compatible with their device. This also means 87 that posting a higher version number APK cancels earlier tests of earlier 88 versions, so posting a production 2.0 version would cancel a beta test of 89 version 1.9 and that beta test would have canceled an alpha test of version 90 1.8. 91 </li> 92 93 <li>Also consider using <a href= 94 "https://www.google.com/insights/consumersurveys/" class= 95 "external-link">Google Consumer Surveys</a> to conduct market research and 96 gather user feedback at scale. 97 </li> 98</ul> 99 100<p style="clear:both"> 101</p> 102 103<div class="dynamic-grid"> 104<div class="headerLine"> 105<h2 id="related-resources">Related Resources</h2> 106</div> 107 108<div class="resource-widget resource-flow-layout col-13" 109 data-query="collection:distribute/googleplay/beta" 110 data-sortOrder="-timestamp" 111 data-cardSizes="9x3" 112 data-maxResults="6"></div> 113 </div> 114