FourteenOnce your closed test qualifies, the Play Console Dashboard shows Apply for production. The form has three parts. Your answers aren't shown publicly, but they're what the reviewer goes on, so specific and true beats long and polished.
Before you start: Play Console can lose your answers if you leave a section before clicking Next. Write your answers somewhere else first, then paste them in.
Part 1: About your closed test
How easy was it to recruit testers?
You pick from a list, and you may be asked how you recruited people. Say where your testers came from.
Example: "I recruited testers through a group of Android developers who test each other's apps, plus three friends and family members."
Did testers use all your features, and did their use match real-world use?
This is the engagement question, and it matters most. Name your main features and how many testers tried each one.
Example: "Testers were assigned short daily tasks. Search: 15 of 15 testers. Watchlist: 14 of 15. New episode alerts: 13 of 15. Most testers opened the app on most days, similar to how we expect real users to check it once or twice a day."
Summarize the feedback, and how you collected it
Say how feedback reached you, then what it said. Real examples help most, especially ones that led to changes.
Example: "After each daily task, testers wrote a short note about what worked and what got in their way. They reported 9 problems and shared 6 ideas. For example, search didn't find shows when the year was typed after the title (fixed), and testers asked to mark a whole season as watched (added)."
Part 2: About your app
Target audience
Describe who the app is for, as specifically as you can.
Example: "Adults who watch several TV shows across streaming services and want one place to see what's airing next."
Your app's value
What it does for people that they can't easily do another way. For games, Google asks what makes your game unique.
Example: "It tracks new episodes across every streaming service and sends a reminder the day one comes out."
Estimated installs in the first year
Pick a realistic range. A big number doesn't help your application.
Part 3: About your production readiness
What did you change based on the closed test?
List real fixes and additions, ideally with the feedback that led to them. This is why shipping an update during your test matters.
Example: "Problems fixed: search now matches titles typed with a year, the calendar no longer skips a day at midnight, and episode alerts no longer arrive twice. Ideas added: mark a whole season as watched."
How did you decide the app was ready?
Explain your bar for "ready", and how you met it.
Example: "All crashes and reported problems were fixed except one minor layout issue. Testers confirmed the main fixes in the last build, and every core feature was used by most testers."
Tips that make every answer stronger
- Use numbers where you have them: testers, days, features tried, problems fixed.
- Lead with what went well, but don't claim anything you can't back up.
- Count what testers chose to report. If every task required a note, "168 notes" mostly counts days. "9 problems and 6 ideas" says more.
- Fix weak spots before you apply. If a feature barely got tested, add a task for it while testers are still around.
Fourteen drafts these answers from your real test data: which features testers tried, what they reported, and what you fixed. It also gives you private tips while there's still time to close gaps. The first cohort begins Saturday, November 14, 2026.
More guides: How to get 12 testers · Why production access gets rejected · How to answer the production access questions
Fourteen is an independent project and isn't affiliated with or endorsed by Google. Google's rules can change, so check Google's help page for the latest. Questions? Email hello@getfourteen.app.