The nine answers of the Google Play production access form
After 14 days with 12 testers, Apply for production opens a form. This page takes its nine questions one by one: what the reviewer is asking, a sentence frame, an example from our own applications and what not to claim. Type your answers in the boxes and the counters keep you under 300 characters.
Google’s help page lists the form in three parts: about your closed test, about your app, and production readiness. It says Google reviews the form and that continued testing may be required if tester engagement was not enough. It does not say how answers are scored, and neither do we know. What we know is what we sent on 26 October 2026 for two of our own apps: those answers are the examples here, with the app names and identifying numbers taken out. Google had not replied when we wrote this.
Our runs Each text box held up to 300 characters in the sources we read, and we wrote to that limit. Google Nothing is saved if you leave the form before Next or Apply, so write the answers here first and paste them in.
Replace every {brace} with a fact from your log. If you cannot, leave the claim out. The counters below warn you while a {brace} is still open. Nothing you type on this page is stored or sent anywhere: it stays in this tab until you close it.
1. How you found the testers
The form asks: How did you recruit testers for your closed test?
The channels you really used, who the testers are, and whether you paid anyone.
We invited testers through Google Groups test communities linked to the closed track, our own Google Group, developer testing groups on Facebook and Telegram, a peer-testing app and test-for-test swaps. Many testers are therefore developers and hobbyists. We used no paid testing service.
Do not write “real users” or “friends and family” if the testers are other developers. Say who they are.
2. How easy it was
The form asks: How easy was it to recruit testers for your closed test?
A choice, not a text box. Pick the one your own log supports.
These were the five choices on our form on 26 October 2026. Our draft had said “Somewhat easy”, which the form did not offer, so open the live form before you decide. We picked Easy, because 12 testers had opted in by the second day.
3. How the testers used the app
The form asks: Describe the engagement you received from testers during your closed test.
Google’s page adds three parts to this question: whether testers used all the features, whether their use looked like real production use, and how it differed. Answer all three in one box.
Google's counter shows 12 testers opted in for 14 days without a break. We asked them to finish the first lesson, make one deliberate mistake and change one setting; two sent reports. Many are developers; we expect real students to practise a few minutes daily for weeks.
Do not give per-person usage numbers you cannot see. Console does not show them, and a made-up figure is the one thing in this form that can be checked against you.
4. The feedback you got
The form asks: Provide a summary of the feedback that you received from testers and explain how you collected it.
The channels that really produced reports, how many reports came in, what each said and what you did about it.
We collected feedback by email and from replies in the group threads; Play's private tester feedback stayed empty. Two reports: the welcome screen opened in English on a Turkish phone, and Play showed "Item not found" on an x86 emulator (we replied).
If Play’s testing feedback page in Console is empty, do not say testers used it. Ours was empty, our first draft said otherwise, and we corrected it before sending. One report with a real fix is worth more than five invented ones.
5. Who the app is for
The form asks: Who is the intended audience of your app?
One sentence about the people, their age range and what they do. It has to agree with your Target audience declaration.
Adults aged 18 and over who record videos, present or give talks: creators, teachers, students and speakers who want a script that scrolls with their voice. This matches the Target audience declaration in Play Console (18 and over only).
Do not name an age group you did not tick in Target audience. Open that page and copy the groups.
6. What the app gives people
The form asks: Describe how your app provides value to users.
What it is, the one thing it does, what a person gets in the first minute, and what is free.
It is a teleprompter that listens and scrolls the script as you read aloud. Record a short take with the camera, then see a delivery report with pace, pauses and filler words. The core is free; voice follow runs on the phone (Android 13 and up). No ads, no account.
No superlatives. Say what it does, in the order a new user meets it.
7. Installs you expect in the first year
The form asks: How many installs do you expect your app to have in your first year?
A choice. Pick the band you could defend if asked.
These were the choices on our form. A new app with no advertising budget belongs in the first band, and we chose it. Our draft had a more precise estimate that the form had no room for.
8. What you changed because of the test
The form asks: What changes did you make to your app based on what you learned during your closed test?
Each change, the report that caused it, the date it shipped and where you checked it. If nothing changed, say so and say why.
In answer to a report that the welcome screen opened in English on a Turkish phone, note names now follow the phone's language. It shipped as an update on 19 Oct and was checked on a physical phone on 20 Oct.
The app code has not changed since the closed-test build: the one report was an emulator install problem, not an app defect. On 21 Oct we corrected the yearly plan's free-trial offers and the store text so the trial length comes from Play and is shown correctly.
This is the honest version for an app where nothing a tester said led to a code change. It is the weaker answer, and we sent it anyway rather than invent a fix. We do not know yet how Google reads it.
Never invent a change. “No code change, and here is why” at least reads true. A made-up fix does not.
9. Why you think it is ready
The form asks: How did you decide that your app is ready for production?
The checks you really ran, with their numbers, the real phone you walked through the release build on, and the Console sections that are complete.
Type checks, 217 unit tests and 86 end-to-end checks passed; the release build was walked through on a Samsung phone on 21 Oct. Android vitals lists no crashes or ANRs. Data safety, content rating, target audience and App access are complete.
Look at Android vitals and the Pre-launch report in Console before you write that nothing crashes. Ours said “Data unavailable” for the crash rate, so we wrote only what the list showed.
All nine, in order. Copy them as one text to keep a record, or download it. It is made in your browser and goes nowhere else.
Where our drafts and the live form differed
We drafted all nine answers days before the form opened and then wrote the final text with the live form in front of us. Four things changed. The lesson is to draft early and to read the real form before you paste.
| Where | What our draft said | What the form needed |
|---|---|---|
| Question 2 | Our draft said “Somewhat easy”. | The form offered five choices and no “Somewhat”. We chose Easy. |
| Question 4 | Our draft said we collected feedback through Play’s private tester feedback. | That page in Console was empty. We rewrote it to the channels that really produced the two reports. |
| Question 7 | Our draft estimated 1,000 to 10,000 installs. | The form had ranges only. We chose 0 to 10K. |
| Question 9 | Our draft listed the checks and the Console sections. | We added the phone walk-through and what Android vitals showed, and cut the sentence about active products to fit. |
Next
- The tracker is where the facts for these answers come from: dates, phones, reports, updates.
- The Console checklist lists what to confirm before you press Apply.
- If the application is rejected, read this before you write the second one.
Source of the form’s structure: App testing requirements for personal developer accounts, Play Console Help, read 27 October 2026. The examples and the differences come from our own applications of 26 October 2026. We do not promise that any answer is accepted: Google decides.