If you've completed Google Play's closed testing requirement, there is one more important step before you can publish your Android app to production: applying for production access.
For applicable personal Google Play developer accounts, you currently need at least 12 testers opted in continuously for 14 days before you can apply.
But completing those 14 days isn't the end of the process.
Google Play asks several questions about:
- how you recruited your testers
- how testers used your app
- what feedback you received
- what you changed during testing
- your target audience
- the value your app provides
- why you believe the app is ready for production
I recently went through this process for my own indie Android app, CalmLingo, so below are the questions I encountered, the type of answer I provided, and some tips for writing your own responses.
Important: Don't blindly copy these answers. Your responses should describe what actually happened during your own closed test.
You can also find the more detailed version of this guide here:
👉 Google Play Production Access Questions and Sample Answers
1. How did you recruit users for your closed test?
Google may ask how you found the people who participated in your test.
This could include:
- friends and family
- colleagues
- existing users
- developer communities
- social media groups
- Android testing communities
- testing platforms
Sample answer
I recruited testers through friends, family, and Android app-testing communities. This gave me a mix of everyday users and developers familiar with testing early-stage apps, which helped me identify usability and reliability issues before release.
How to answer
Be specific about where your testers actually came from.
There's no need to make your testing process sound more sophisticated than it was. If you used friends, say so. If you used an Android testing community or platform, mention it.
The important thing is that your answer matches what actually happened.
2. How easy was it to recruit testers for your app?
This is usually a multiple-choice question with options such as:
- Very difficult
- Difficult
- Neither difficult nor easy
- Easy
- Very easy
My answer
I selected:
Easy
There isn't a universally correct answer here.
A developer with an existing community may find recruiting testers easy, while a solo developer publishing their first app might find it extremely difficult.
Choose the option that best represents your experience.
3. Describe the engagement you received from testers during your closed test
This is one of the more important questions.
Google isn't only interested in whether people joined your test. It wants to understand how testers interacted with the app.
For CalmLingo, the important user journey involved:
- signing in
- selecting language-learning preferences
- playing audio content
- reading or listening to stories
- completing quizzes
- replaying content
- testing on different Android devices
Sample answer
Testers used the main user journey, including sign-in, selecting preferences, playing audio content, completing quizzes, and navigating the primary learning screens. Some also shared screenshots from different Android devices. Their usage was similar to how I would expect normal users to interact with the app.
How to answer
Instead of writing:
Testers used the app regularly.
Explain what they actually did.
For example:
Testers created accounts, completed onboarding, created projects, edited items, exported results, and returned to the app on multiple days.
The exact activities should depend on your app.
4. Provide a summary of the feedback that you received from testers
Google also asks what your testers told you and how you collected that feedback.
This is a good opportunity to demonstrate that your closed test actually helped improve the app.
During my CalmLingo test, testers reported issues including:
- problems with Google sign-in
- audio playback occasionally stopping
I fixed these through updates during the closed-testing period.
Sample answer
I collected feedback through direct messages and screenshots. Testers reported an issue with Google sign-in and another problem where audio playback could occasionally stop. I fixed the sign-in issue in one update and improved audio playback reliability in a subsequent update.
How to answer
A useful response usually covers three things:
- How you collected feedback
- What testers reported
- What you did about it
Feedback could have come through:
- WhatsApp or Telegram
- Discord
- testing communities
- surveys
- screenshots
- screen recordings
- issue trackers
- an in-app feedback feature
Don't feel that all feedback needs to be positive.
Finding bugs during closed testing is actually useful because it demonstrates that testing resulted in improvements.
About Your App
The next group of questions focuses less on your testing process and more on the app itself.
5. Who is the intended audience of your app?
Avoid answering with something extremely broad like:
Everyone.
Instead, describe the people most likely to benefit from your app.
Sample answer
For CalmLingo, I used an answer along these lines:
CalmLingo is designed for people learning French or Spanish, particularly beginner and intermediate learners who want relaxed listening practice using stories, dialogues, podcasts, and meditation-style content.
How to answer
Think about:
- Who has the problem your app solves?
- What experience level do they have?
- What are they trying to accomplish?
- In what situations would they use your app?
For example, instead of:
My app is for people interested in fitness.
You could write:
The app is intended for beginner runners who want simple training plans and progress tracking while preparing for their first 5K.
That's much more informative.
6. Describe how your app provides value to users
This question isn't asking for a list of features.
Google wants to understand why those features are useful.
Sample answer
CalmLingo helps learners improve their French or Spanish through level-appropriate listening content such as stories, dialogues, podcasts, and meditations. The app provides a relaxed way to build vocabulary, listening confidence, and regular exposure to the language.
Notice the difference between saying:
The app has stories, quizzes and audio.
and:
The app uses stories, quizzes and audio to help learners improve listening comprehension and vocabulary.
The second version explains the value.
A useful structure is:
Problem → Experience → Benefit
7. How many installs do you expect your app to have in your first year?
You may be given ranges such as:
- 0–10K
- 10K–100K
- 100K–1M
- 1M+
- I don't know
For my indie app, I selected:
0–10K
Again, there is no single correct answer.
Try to be realistic.
If you're a solo developer launching a new app without an existing audience, choosing the lowest range can be completely reasonable.
If you already have a large customer base or significant marketing distribution, your estimate might be higher.
Production Readiness
The final questions are particularly important because they help explain what you learned from testing and why you're ready to launch.
8. What changes did you make to your app based on what you learned during your closed test?
Don't simply write:
I improved the app based on tester feedback.
Explain the actual changes.
Sample answer
Based on feedback from the closed test, I fixed a Google sign-in issue in one update. I later improved audio playback reliability by resolving a problem that could cause playback to stop until the user reopened the app.
Other things you could mention include:
- crash fixes
- UI improvements
- confusing navigation you simplified
- authentication problems
- performance improvements
- compatibility fixes
- accessibility improvements
- error handling
- unclear onboarding
- layout problems on certain devices
The strongest responses connect the feedback directly to the change:
Tester problem → Your fix
For example:
Testers found the pagination controls confusing, so I replaced the dots with numbered step indicators.
That's much more convincing than:
Improved navigation.
9. How did you decide that your app is ready for production?
Finishing 14 days of testing doesn't automatically mean your app is ready.
Your answer should explain why you believe the important parts of the app are now stable enough for real users.
Sample answer
I considered the app ready for production after completing the closed test, reviewing tester feedback, fixing the main issues that were reported, and confirming that the core user journey worked reliably across the devices used during testing.
You could consider things such as:
- Does the main user journey work?
- Have blocking bugs been resolved?
- Does authentication work reliably?
- Can new users understand the interface?
- Did you review the feedback you received?
- Did you test important features on different devices?
- Are crashes or major reliability problems resolved?
You don't need to claim that your app is perfect.
You need to explain why it's stable enough for wider use.
A Few Tips Before You Submit
Be specific
Instead of:
Testers tested all the features.
Try:
Testers completed onboarding, created accounts, added items, edited them, and tested the main export flow.
Specific answers make it much easier to understand what happened during your closed test.
Talk about actual engagement
Don't focus entirely on finding 12 testers.
The application also asks what happened after those testers joined.
Mention meaningful interactions with the app.
Mention bugs you discovered
Finding a problem during testing isn't necessarily a bad thing.
That's one of the reasons closed testing exists.
A response like:
Testers found a sign-in bug, so I identified the cause, released an updated build, and confirmed that the sign-in flow worked afterward.
shows a much more meaningful testing process than simply saying:
Everything worked perfectly.
Don't copy sample answers word-for-word
Your answers should reflect your own:
- app
- audience
- testers
- features
- feedback
- bugs
- updates
- testing process
Use examples like these to understand what information to include, then adapt the wording to your own situation.
The Hard Part: Knowing Whether Testers Actually Tested
One problem I ran into with closed-testing communities was visibility.
Finding people willing to opt into a test is one thing.
Knowing whether they actually installed and used the app is another.
Many tester-exchange platforms rely on screenshots or users manually telling each other that testing has been completed. I wanted a clearer way to understand tester activity.
That's one of the reasons I built TestFlock.
TestFlock automatically verifies app installation and usage time, so developers can see how much time their testers actually spent using the app.
It also combines two approaches that are normally separated:
- Flocks — groups of up to 16 developers testing one another's apps
- FlyMates — 1:1 tester exchanges that can be used to find additional or backup testers
So you can join a testing group while still having the flexibility to find individual testers when needed.
The aim isn't just to collect 12 opt-ins. It's to make the closed-testing process easier to track and encourage more meaningful testing and feedback.
Final Thoughts
The Google Play production access application can look intimidating the first time you see it, but the questions are quite logical.
Google essentially wants to understand:
Who tested your app?
What did they do?
What feedback did they give you?
What did you change?
Why do you believe the app is now ready?
If you've genuinely used the closed-testing period to test your core flows, gather feedback, fix problems, and improve the app, you already have most of the information you need.
You just need to describe it clearly.
For the complete question-by-question guide, you can read:
👉 Google Play Production Access Questions and Sample Answers: Complete Guide
If you're still looking for Android testers for your closed test, you can also check out TestFlock.
