If your personal Google Play developer account was created after 13 November 2023, finishing the closed test (at least 12 testers opted in for 14 days in a row) doesn't publish your app by itself. You then get an Apply for production button in Play Console, and a short questionnaire. Google reviews your answers, usually within about a week, and a vague application is one of the most common reasons people get sent back for another round of testing.
I run App Circle, a free test-for-test community for Android devs, and the question we hear most after "where do I find 12 testers?" is "what do I actually write in that form?". Here's a plain-English walk-through of each section and what a good answer looks like.
Part 1: About your closed test
How easy was it to recruit testers?
Be honest. "Fairly hard. I recruited friends and a developer test-exchange community, invited 17 people so I had a buffer, and 14 stayed opted in for the full 14 days" is much better than "Easy". Google isn't marking you down for finding it hard. It wants to know the test was real.
Describe the engagement you received from testers.
This is where most weak applications fall down. Give specifics:
- roughly how many testers used the app on more than one day,
- which features they tried,
- whether you saw crashes or ANRs in Android vitals during the test.
If your testers only installed the app once and never opened it again, fix that before applying. Ask testers to open the app on several different days and do one or two real tasks.
Summarise the feedback you received.
List 3 to 5 concrete points, good and bad. For example: "Two testers found the sign-up screen confusing; one reported the timer resetting when the screen rotated; several liked the offline mode." Specific beats polite.
How did you collect feedback?
Name the channel: the Play Store private feedback, a Google Form, email, a Discord channel, in-app feedback. Any of these is fine. "I didn't" is not.
Part 2: About your app
Who is the intended audience? One or two sentences. "UK hobby gardeners who want watering reminders" is better than "everyone".
How does your app provide value to users? Describe the problem it solves, not the tech stack.
How many installs do you expect in your first year? Pick a realistic range. A small indie app saying "10,000 to 50,000" with no marketing plan reads oddly; "under 10,000" is perfectly acceptable.
Part 3: Your production readiness
What changes did you make based on what you learned during the closed test?
Google wants evidence you listened. Link each change to feedback: "Fixed the rotation bug reported by testers in version 1.0.3; simplified sign-up to one screen after two testers got stuck." If you shipped at least one update during the test, mention its version number.
How did you decide your app was ready for production?
Mention stability (crash-free in vitals for the last week of testing), that the main feedback points were fixed, and that your store listing, privacy policy and content rating are complete.
Common mistakes that lead to "your app needs more testing"
- One-line answers. Every box deserves at least two or three sentences.
- No updates during the test. Shipping zero changes in 14 days makes "what did you change?" hard to answer.
- Testers who never opened the app. Opted in for 14 days is the minimum, not the whole story.
- Removing testers or the tester list near the end. Keep everything in place until you've been approved.
- Copy-pasted answers from a template. Write about your app and your testers.
If you're rejected
You'll usually be asked to keep testing for a further period and reapply. Use that time to get more genuine engagement, ship an update based on feedback, and rewrite your answers with specifics. It isn't a ban, just a "not yet".
Getting testers who actually use the app
The form rewards real engagement, so it's worth testing with people who will open your app more than once. App Circle is free: you test other developers' apps, earn virtual coins (no real money), and spend them on testers for your own app, with tests running 15 days to give a one-day buffer over Google's 14. There's a full guide to the 14-day rule here: Google Play's 14-day closed testing rule explained.
Whatever route you take, recruit a few more than 12, give testers small tasks, and keep notes of their feedback from day one. Those notes are most of your production access application.
Disclosure: I run App Circle.
Top comments (0)