PeerPlay
PeerPlay exists because of one rule. I ran into Google Play's closed-testing requirement with my own Android app, needed 12 testers who stayed opted in for 14 days, and could not find them. So I built an app where developers test each other's apps in tracked 14-day rounds, with a check that each tester actually opened the app for a real minimum session.
Then I wrote about it on Indie Hackers, and the most useful replies were not about the thing I had built. They were about the walls on either side of it.
Pushback one: the harder wall comes after day 14
Several readers said the same thing in different words. Passing closed testing gets you into production, and production for a new app means zero ratings and almost no search visibility. The 12-tester rule is a gate with clear instructions. What comes after has no instructions at all.
It is obviously true, and I had treated production access as the finish line. For the developers using PeerPlay it is the starting line. An app that passes testing and then sits unseen in the store has solved a requirement, not a problem.
Pushback two: some developers never hit the rule
One reader pointed out that an organization developer account with a DUNS number skips the 12-tester rule altogether. The requirement applies to newer personal accounts, so a developer who registers as an organization can go a different way.
That doesn't make PeerPlay pointless. Plenty of solo developers can't or don't want to register a company just to publish an app. But it changed how I talk about the problem. The honest version is: if you are a solo developer on a personal account, here is how to get through it. If you have a registered business, look at an organization account first.
Pushback three: what keeps testers around after day 15?
The sharpest question was simple. Once the 14 days are done, why would a tester keep using your app? In a test swap, everyone has done their part. Nothing pulls them back.
I had real numbers to look at here. PeerPlay's first paid campaign, for a women's health and cycle tracking app called Nada, ran from September 16 to October 6, 2026. 18 testers joined, 11 completed all 14 days and 3 quit. At least 12 testers were active every day from September 17 to October 1, and Google granted production access. Testers also sent 14 feedback items, and the developer marked 8 as solved during the test.
That is a good testing result. It says nothing about day 15. A campaign built to satisfy a 14-day rule will, by design, end on day 14.
What I have done since
One change is the Play Store listing. On October 10, 2026 I rewrote it around the problem people actually search for. The title is now "PeerPlay: 12 Testers, 14 Days". Before the change the app had 1K+ installs and a 4.7 rating from 31 reviews, so that is the baseline I will compare against.
Another is about ratings, the wall that comes after testing. I drafted an in-app review prompt for PeerPlay that only asks for a rating after a developer's campaign has completed, at most once per campaign and once per 30 days. It is not released yet. The idea is to ask at the moment someone has just received what they came for, not on a timer.
The last is in how I write about all of this. Getting through closed testing is still the job PeerPlay does. But I now say plainly that it is the first wall, not the last one.
The lesson for anyone building for developers
Post your thing where people will argue with you. I knew the 12-tester rule inside out because I had lived it. What I could not see from inside was what came before and after it for other people. Three replies on a forum showed me more about the problem than my own experience of it had.
FAQ
Is passing Google Play closed testing enough to get downloads?
No. It gets you production access. A new app then starts with zero ratings and little search visibility, so plan for ratings and discoverability before day 14 ends.
Can an organization account skip the 12-tester rule?
Yes. The 12 testers for 14 days requirement applies to newer personal developer accounts. An organization account, which needs a DUNS number, does not have it.
How many testers usually finish a 14-day closed test?
It varies. In PeerPlay's first paid campaign, 18 testers joined, 11 completed all 14 days and 3 quit, which is why recruiting above the minimum 12 matters.
When should an app ask users for a rating?
Right after the user has gotten real value, not on a timer. For PeerPlay that is after a developer's testing campaign completes.