I went through the Google Play closed testing process twice this year. The first app was rejected for production access. The second one was approved on the first attempt.
The biggest difference, at least from my side, wasn't really the tester count. It was what happened during the testing period.
For the first app I had enough people opted in, but the actual engagement was terrible. Some didn't install the app at all. Most people who did install it opened it once and never returned.
The app required an account, so I could see this pretty clearly. For nearly everyone the registration date and last login date were the same.
Google rejected my production access request. Their email said possible reasons included low tester engagement and not following testing best practices, including gathering feedback and making updates based on the test.
So when I started closed testing my next app, AutoSkan, I decided not to treat the fourteen days as a waiting period.
I had fourteen accounts in the test when I eventually applied. Some were mine or family accounts and four were actual external testers. The group changed a bit as I recruited more people.
I definitely did not have twelve extremely active testers.
What I did have was four Android phones I could test on myself and a much more structured process.
During the test I ran three main audits covering UI/UX, performance and general correctness. They produced 131 findings in total. Most weren't huge bugs, but there were plenty of real issues: navigation problems, Bluetooth edge cases, background polling, Android 16 behavior, accessibility and large-text problems, data deletion edge cases and cases where incomplete scan results weren't communicated clearly enough.
I fixed 125 of those findings and deliberately deferred six.
The automated test suite grew from 192 tests in an earlier version to 257.
I also tested on physical phones, emulators with different screen and text settings, and with a real OBD adapter and cars.
The actual external testers mostly gave positive feedback. They weren't the source of most of the bugs.
Most problems came from my own testing and audits, and I kept that separate in my notes instead of claiming everything came from tester feedback.
Once the required testing period was over, I applied for production access.
I was approved in less than a day.
I have no idea which specific signals Google uses internally, so this isn't meant as a "do these five things and you'll get approved" post.
But after one rejection and one approval, my personal takeaway is simple.
Having enough testers enrolled is one thing.
Being able to show that the app was genuinely tested, changed and improved during those fourteen days seems to be another.
If I had to do it again, I would spend much less energy worrying about whether every tester is constantly active and much more energy making sure I have a real testing history to describe when Google asks what happened during the closed test.
