How to Get 20 Testers & Pass Google’s New App Review Policy

At BetaTesting, we’re happy to announce our new pre-submission test type, designed to help developers recruit 20 testers for 2 weeks of app testing so you can pass the Google Play app store submission requirements with flying colors!

Check out our new Google Play 20 Tester Pre-Submission Beta Testing test type.

Here’s what you’ll learn in this article:

1. How to recruit 20 targeted testers for your Google Play app
2. How to get 2 consecutive weeks of testing
3. How to collect survey feedback and bug reports to improve your app and pass the Google Play app submission requirements
4. How to apply to publish your app in production on Google Play and how to answer questions to pass your app review!

---

About the New 20 Tester Google Policy

Where can I learn about this policy? Check out the new updated developer app submission requirements on Google Play. These are designed to improve the quality of apps within Google Play. Part of these requirements include app testing before submitting your app for review to the Google Play store. This is required for all new personal developer accounts, and recommended for all developers and organizations!

New requirements include the following:

• Personal developer accounts must first run a closed test for your app with at least 20 testers who have opted in for 14 days or more before submitting your app for approval.
• After meeting this criteria, you can apply for production access on in the Play Console
• During the application process, you’ll be asked questions about your app and its testing process and production readiness. In this process, you can reference your testing process with BetaTesting to collect bugs and feedback.

---

How to recruit 20 testers for your Google Play app

At BetaTesting, we have a community of over 400,000 testers around the world, with roughly 200,000 available in the United States. We allow targeting in a wide variety of ways:

• Demographic targeting: Age, gender, income, education and many more.
• Device targeting: Target users on Android phones, Android tablets, and many more device platforms (iPhones, iPads, Windows, Mac, etc).
• Custom screening surveys: Ask questions to testers and only those that answer the right way will be accepted.

You can learn all about our tester recruiting here. Check out our testing package for Google Play 20 Tester Pre-Submission Beta Testing.

Collect emails and distribute your app for closed testing through the Google Play Console

Through our pre-submission test template, you can collect emails from test participants when they join your test. You can then view or download the list of applicants so you can easily distribute your app through the Google Play Console. When designing your test, we allow you to collect emails when choosing which platforms you’d like to distribute your app to:

Screenshot below:

---

How to get testers to engage for 2 consecutive weeks of testing

Through the BetaTesting platform, we have multi-week test options available, designed specifically to recruit and engage testers over multiple weeks.

We provide two options for setting up your test:

1. Use our pre-designed template, which requires ZERO setup and can be launched within minutes.
2. OR customize your test instructions and survey questions according to your app.

If you choose to customize your test design, you can build your own test workflow using our custom test builder:

Watch the video below to learn more about how multi-day testing on BetaTesting works:

---

Want to learn more about our pre-submission Google Play app testing?

---

How to get user feedback & bug reports to improve your app before submission

View & manage your bugs through two different views.

The bug management “Grid View”

The bug management “Detail View”

View survey results along with automated AI analysis to save you hours.

---

How to apply to publish your app in production on Google Play and how to answer questions to pass your app review!

When applying for access to Google Play Production, you’ll be asked the following questions:

Part 1: About your closed test

This section is used by Google to determine whether or not your app has met requirements to be tested before it is published on Google Play. The purpose is to allow Google to validate that your app is high quality and prevent low quality apps from being published in the Play Store. In this section, you should provide the following information:

1. Provide information on how easy or difficult it was to recruit testers for your app. Hopefully, this was very easy for you if you used BetaTesting for your pre-submission test!
2. Provide details about how testers engaged with your app. You can include details about any tasks or instructions you provided, and which features testers engaged with. As evidence for this section, you can also provide details on the bug reports you collected and resolved, and specific feedback and charts from your final feedback survey collected through BetaTesting. You can also indicate whether or not testers were able to engage with your app similarly to how a production user might in the real Play Store. With BetaTesting, we allow our testers to use your app organically over two weeks, so the types of usage and interactions should be close to (but even more rigorous) than normal app users.
3. You’ll be asked to summarize the feedback you received from testers. This is a great spot to provide details from the various charts and feedback you received through your final feedback survey report. Common metrics to reference include your NPS score or star rating, and you can also share the automatically-generated AI summaries that summarize tester’s feedback for each question.

Part 2: About your app or game

This section is used by Google to understand a bit more about your app or game as part of their consideration during your app review process. You should provide the following info:

1. Describe the intended use of your app or game and what type of user you are targeting. Be specific but also keep it short and sweet.
2. Describe what makes your app or game stand out, and what value you provide to users. What is unique about your product and why will users use it? In this section, you can point to positive feedback you received during your beta test, and specifically reference answers to the questions in your feedback survey.
3. Estimate how many installations you expect in the first year. Try to make the estimation reasonable, but don’t underestimate! However, with very high numbers, your app may receive a more strict review from Google given that they want to ensure your app is high quality if you expect so many people to install it.

Part 3: Production Readiness

This section is used to provide evidence that your app is ready for production. You should provide the following info:

1. Describe the bugs you fixed during the testing period and any improvements you made to the app during the closed testing process.
2. Describe why you are confident that your app is ready for production. Good examples would be positive feedback, a good NPS score, low number of new bug submissions (or validating that many key bugs have been resolved), or running multiple iterative tests over time and showing improvement.

Get in touch today to run your pre-submission test to ensure you pass the Google Play review!

Have questions? Book a call in our call calendar.