PeerPlay
On October 19, 2026 a game developer asked me a simple question: could PeerPlay's free route get their game through Google Play's closed testing requirement? The game was a 1.6 GB download.
The honest answer was yes, it can work, but with a catch most game developers don't think about until their tester count stalls. Every tester has to download the whole game before they can count toward your 12. With a small app that is a few seconds. With 1.6 GB, it is a decision.
Why size matters more in a closed test
For newer personal developer accounts, Google asks for at least 12 testers opted in to your closed test for 14 days in a row before you can apply for production. Those testers are not fans who went looking for your game. They are friends, other developers or people doing you a favor.
A real player who wants your game will wait for a big download. Someone doing you a favor on mobile data, with a phone that is nearly full, often will not. They may opt in and never install, or install, see the storage warning and quit. Both cost you a tester before the 14 days have properly started.
What the free exchange really asks of testers
PeerPlay's free route is a 1-for-1 exchange: you test other developers' apps, and they test yours. Each tester opens the app from PeerPlay for about 30 seconds a day, every day for 14 days. For a typical utility app, that is an easy deal.
For a 1.6 GB game, the daily part is still easy. The first step is not. Every exchange partner has to download 1.6 GB to hold up their end, and I told the developer plainly that some of them will skip it. That is not a PeerPlay problem, it is true of any swap group, Discord server or tester community. People pick the apps that cost them the least.
PeerPlay does not show the download size automatically, so my suggestion was simple: put "1.6 GB download" in the app description when you add the game. A tester who joins knowing the size is far more likely to stay than one who finds out halfway through the install.
How to make a big game easier to test
Say the size up front, everywhere. In the opt-in message, in the description, in the swap request. Add "best on Wi-Fi" if it helps. Surprises are what make people quit.
Make the test build as small as you can. If your game ships large assets, look at Play Asset Delivery, which lets you split assets into packs that download at install time, right after install or on demand. Check Google's current documentation for the size limits that apply to your setup. Even without that, a closed test build does not need every level, every language and every cinematic. A smaller build that covers your core loop is a better test anyway.
Recruit well above 12. With a small app, a few extra testers is a sensible buffer. With a big game, plan for more of the people who say yes to never get past the download, and recruit with that in mind.
Check your opted-in count in Play Console every day for the first few days. The drop-off for big games happens early, so that is when you need to react.
Thirty seconds is not a playtest
There is a second catch for games. Opening the app for 30 seconds keeps a tester counted, but it tells you almost nothing about your game. You learn whether it crashes on launch. You do not learn whether level three is too hard, whether the tutorial makes sense or whether the frame rate falls apart after ten minutes.
Google's production application asks what you learned from testing and what you changed. For a game, the strongest answers come from people who actually played. So give testers one or two concrete things to try, like finishing the first level or playing one full session, and ask for one line of feedback after each.
For developers who need that kind of feedback, I added a VIP Game Playtest package to PeerPlay on the same day, as early access: 15 real players, each playing at least 15 minutes and sending written feedback every day for 14 days. It is new and requested by email, so I can't share results from it yet. The free exchange still works for games, as long as you go in knowing what it asks of your testers.
FAQ
Does a large download size affect Google Play closed testing?
Not the rules, which are the same for every app. It affects your testers: some will not download a very large game, so you can lose testers before they ever count toward your 12.
How many testers should I recruit for a big game?
Well above 12. Expect more drop-off at the download step than with a small app, and check your opted-in count daily in the first days.
Can I use a smaller build for closed testing?
You can ship a lighter closed test build, for example with fewer levels or assets, as long as it is the same app. A smaller build that covers your core loop is easier to install and still gives you useful feedback.
Is opening the game for 30 seconds a day enough?
It keeps a tester active, but it gives you little feedback. For games, ask testers to play a real session and send a line of feedback, so you have something concrete for the production application.