Short answer: testers can send private feedback through Google Play, which you'll find in Play Console under Monitor and improve, then Ratings and reviews, then Testing feedback. Add one channel of your own, keep a simple log, and you'll have the summary Google asks for when you apply for production access.
Where Play Console puts tester feedback
Google's steps: sign in to Play Console, select your app and open the Testing feedback page. You can filter by date, language, reply state, app version or device type, and search for keywords. You can also reply to testers.
Add a second channel
Google suggests a clear feedback channel such as email, a website or a messaging forum, and even a group chat where testers can see each other's reports. A form with three fields (what you did, what you expected, what happened) gives you structured reports and space for screenshots.
Keep a feedback log
Google's tip is to maintain a record of feedback and review it regularly. A spreadsheet is enough:
| Date | Tester | Device / Android | Issue | Severity | Status | Fixed in |
|---|
Add every report, even duplicates. Duplicates show which issues matter most.
Turning the log into your summary
Group by theme
Crashes, layout, confusing flows, feature requests.
Lead with what you fixed
"Testers reported a crash when switching tabs quickly on Android 13; fixed in 1.0.4."
Be honest about what you didn't change
"Two testers asked for a widget; we've scheduled it for after launch."
Mention how you collected it
Play testing feedback, a form and a chat group.
Make feedback easier to give
Testers send more when it's easy. Pin the form link in your brief, ask a specific question every few days and thank people quickly. TestLancer's guide on getting useful user feedback covers question wording.
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
- Recruiting exactly 12. One opt-out and you're back to waiting.
- Running the test on the internal track. Internal days don't count toward the requirement.
- Sharing an APK instead of the opt-in link. Testers must opt in and install from Google Play.
- Tidying the tester list mid-test. Removing someone ends their streak.
- Shipping no updates. The production readiness section asks what you changed because of testing.
- Using friends who never open the app. Google can ask for more testing when engagement is low.
- Buying reviews or ratings. They break Google Play policy and give you nothing to report. TestLancer never sells them.
FAQ
Is testing feedback public?
No. Google describes it as private feedback from testers.
Can I count bug reports from internal testers?
You can mention them, but the application is about your closed test, so focus on closed-test feedback.
How much feedback is enough?
There's no published number. Aim for feedback that covers every main feature and at least one change made because of it.
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.
Top comments (0)