How to Answer Google Play's Production Access Questions (With Honest Examples)

Short answer: the production access application has three parts: About your closed test, About your app/game, and About your production readiness. Good answers are specific and based on what actually happened in your closed test: who tested, what they used, what they reported, and what you changed. Below is each question with an example of the level of detail to aim for.

Part 1: About your closed test

Google says this section helps verify that apps were thoroughly tested, which protects users from low-quality apps, malware and fraud.

How easy was it to recruit testers?

Pick the honest option. It doesn't need defending.

Did testers use all the features? Did usage match real users?

Example: "Most testers completed sign-up, created a workout and used the timer. Few used data export, which we expect to be a minor feature in production too."

Summarise the feedback and how you collected it

Example: "We collected feedback through Play's testing feedback and a shared form. The main issues were the timer resetting when the screen locked and unclear text on the paywall screen."

Part 2: About your app/game

Google says these answers aren't shown publicly and don't affect visibility or feature access.

Target audience

Be specific: "Adults who do home workouts three or more times a week" is better than "everyone".

Value proposition

For apps, explain how it provides value. For games, what makes it unique.

Expected installs in year one

Choose a realistic range.

Part 3: About your production readiness

Changes made because of the test

Example: "Version 1.0.3 fixed the timer reset, rewrote the paywall copy, and added a dark mode toggle requested by testers."

How you decided it was ready

Example: "No crash reports in the last five days of testing, all core flows completed by testers on Android 12 to 14, and the feedback we received was minor."

Important: Google warns that if you click Discard or leave without applying, your answers aren't saved. Draft them in a document first.

Answers that weaken an application

One-line answers such as "testing went well", claims you can't support, and copied text. If you ran a thin test, the honest fix is a better test. TestLancer's production access guide has a template you can adapt.

The official rules, in one place

According to Google's Play Console Help article on app testing requirements for new personal developer accounts:

• The rule applies to personal developer accounts created after November 13, 2023.
• You must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days.
• Production and Pre-registration stay disabled until you meet the requirement; you then apply for production access from the Dashboard.
• The application has three parts: About your closed test, About your app/game and About your production readiness.
• Review usually takes seven days or less, but can take longer. If engagement was too low or you had fewer than 12 opted-in testers, Google may ask you to keep testing.
• Testers who opt out before 14 days don't count, and if someone opts out and back in, their 14 days must be consecutive.

Quick checklist before you apply for production access

• [ ] At least 12 testers opted in today, each for 14 or more days in a row (check your log, not your memory).
• [ ] A buffer of extra testers in case someone drops out at the last minute.
• [ ] Notes on which features testers used, and whether that matched how you expect real users to behave.
• [ ] A short summary of the feedback you received and how you collected it (Play testing feedback, a form, a chat group).
• [ ] A list of changes you made because of the test, with version numbers.
• [ ] Working test credentials in Play Console if your app needs a login.
• [ ] Content rating, target audience and data safety answers that match the real app.
• [ ] No crashes or empty screens on the build you're about to ship.

If any box is empty, a few more days of testing usually costs less than another review cycle.

Mistakes that cost developers extra weeks

1. Recruiting exactly 12. One opt-out and you're back to waiting.
2. Running the test on the internal track. Internal days don't count toward the requirement.
3. Sharing an APK instead of the opt-in link. Testers must opt in and install from Google Play.
4. Tidying the tester list mid-test. Removing someone ends their streak.
5. Shipping no updates. The production readiness section asks what you changed because of testing.
6. Using friends who never open the app. Google can ask for more testing when engagement is low.
7. Buying reviews or ratings. They break Google Play policy and give you nothing to report. TestLancer never sells them.

FAQ

Are my answers public?

Google says the About your app/game answers aren't displayed publicly.

How long should answers be?

Long enough to be specific: a few sentences with real examples and version numbers.

What if I received very little feedback?

Say so honestly, then consider running the test longer with more engaged testers before you apply.

Next step

If you can't find 12 reliable people on your own, TestLancer's Google Play closed testing service runs a 14-day closed test with real testers who opt in, use your app and send feedback you can summarise in your production access application. You can also use the free Google Play Launch Center checklist first. TestLancer does not sell reviews, ratings or installs, and no one can guarantee Google will approve production access. Your app still has to meet Google Play policy.