Free HTML to New personal developer accounts on Google Play must run a closed test with at least 12 testers for 14 days in a row before they can publish to everyone. When the test is done, the Apply for production button opens a short questionnaire. Many developers rush it, get a rejection and have to test for another 14 days.
We went through this ourselves for our own app, so here are the questions, what Google is looking for in each, and example answers you can adapt. Each answer box allows about 300 characters, spaces included, so short and specific wins.
Part 1: About your closed test
How did you recruit users for your closed test?
Google wants to know if your testers were real people likely to use the app. Friends, family, colleagues, customers and online communities are all fine. Say who they were and why the app made sense for them.
I recruited testers through a closed testing group and from friends who already use apps like this one. Since they were interested in this category, they used the app regularly, tried the main features and shared honest feedback, which helped me fix bugs before launch.
How easy was it to recruit testers?
Be honest. "It took about a week to find 12 people who would really use it" is a perfectly good answer.
Describe the engagement you received from testers
This asks whether testers used the features and whether that looked like real use. Name your app's actual features, and mention any difference from how real users will behave.
Testers were active through the test and used most features: building apps from a website, ZIP or HTML, templates, icons and dark mode. Usage was like real users, though testers tried more features; real users will mostly build one app.
If some features were not used, say so. "Most testers used the core features, but only a few tried the export option" reads as honest, which is what you want.
Provide a summary of the feedback you received, and how you collected it
Mention the channel (email, a feedback form, an in-app chat, a WhatsApp group, Play's private feedback) and two or three real issues.
We collected feedback through in-app chat, email and crash reports. Testers reported a download saved with the wrong file name, dark mode problems in menus and squeezed text in some languages. We fixed all of these before applying.
Part 2: About your app
Who is the intended audience of your app?
Describe people, not demographics. Who has the problem your app solves?
Describe how your app provides value to users
One or two concrete benefits. What can a user do with your app that they could not easily do before?
How many installs do you expect in your first year?
Pick a realistic range. Nobody is graded on ambition here.
Part 3: Your production readiness
What changes did you make to your app based on what you learned?
This is the most important answer, and the most commonly weak one. Google wants proof that the test was used to improve the app. List real fixes, and make sure you actually uploaded new versions during the test: a test with one upload and no changes looks like waiting out the clock.
Based on tester feedback, we fixed downloads saving with the wrong name, made bars and menus follow dark mode, fixed a blank page after going offline, fixed squeezed text in some languages and added a hide scroll bar option.
How did you decide that your app is ready for production?
Point to evidence: issues fixed, stable crash reports, testing on real phones, testers able to complete the main task.
We fixed every issue testers reported, tested builds on several real phones, and crash reports showed no new problems after the last update. Testers could complete the main task without help, so we felt it was ready.
Common reasons for a rejection
- Testers did not stay opted in for the full 14 days, or barely opened the app.
- No updates during the test. Ship at least one or two improved builds while testers are active.
- Vague answers such as "testers liked the app and gave good feedback".
- Answers that do not match the app, for example listing features that are not in it.
If you are rejected, Google tells you to keep testing. Use the time to fix something real, upload it, and apply again with specific answers.
Before you apply
- Check the closed test shows at least 12 opted-in testers and 14 days completed.
- Write down three real pieces of feedback and three real changes before you open the form.
- Draft your answers in a notes app first, and count the characters.
- Make sure your store listing, privacy policy and Data safety form are complete, and declare your trader status while you are in Play Console.
Still setting up the test itself? Our closed testing guide covers finding testers and running the 14 days, and the Google Play guide covers the rest of publishing.