
Peerplay
12 Testers, 14 Days Closed Testing for Android Developers
I built PeerPlay to solve my own problem: Google Play requires new personal developer accounts to run a closed test with 12 real testers, active for 14 straight days, before it will grant production access. I had zero testers and no audience when I hit that wall, so I built a place where developers test each other's apps instead of relying on strangers' goodwill or paying for fake activity.
117 campaigns have now completed the full cycle through the app. Before writing this, I went back through every single completion note developers left, because I wanted to know honestly whether this was actually working or whether people were just leaving the moment they technically hit day 14. Some of what's actually there:
"2 million thanks to the developer of this app. without you my app wouldn't be granted access to production. I had recommended about 10 persons to use your app and they also got access to production. this is the best app." That line — the fact that he then referred roughly 10 other developers on his own — is the whole thesis of the product working. Reciprocity creates its own distribution if the mechanic is real instead of decorative.
Not everyone had a smooth ride, and the honest ones told me more than the thank-yous did:
"unfortunately I only had 4 consistent testers out of the 19 [...] it would have been nice to have people actually test the apps features." That's someone who hit the number requirement Google asks for, but not the actual point of testing — a gap I think about constantly, because Google's 12/14 rule checks a headcount, not whether anyone actually used the app.
"our Google account was disabled for several weeks, so we were locked out and didn't have access to this app. But we really appreciate all the feedback we received: we were made aware of some issues with our OAuth login setup and were able to address them." That's from a developer whose account got suspended mid-test, and who still came back to say the testers had already caught a real bug before the suspension even happened.
And one that's basically a review of the exact mechanic the whole product is betting on: "Got testers very fast cause i also tested their apps and all testers were active." The people who reciprocate immediately get reciprocated back immediately. The ones who treat it as a one-way ask don't.
What I didn't expect going in: how many notes read like someone surprised that a free system with no payment and no account-selling actually held together. A handful compare it, unprompted, to a paid-testers experience they'd had before, and not favorably for the paid version.
I'm not going to pretend 117 is a huge number, or that every cycle went perfectly. Some testers no-show. Some developers quit mid-campaign — there's a whole mechanic in the app now (a quit counter, visible but not punitive) that exists specifically because of that pattern showing up early and often. Ghosting is the default failure mode of any exchange system, and I spent more engineering time on the anti-ghosting logic than on almost anything else in the app.
But it's 117 real Play Store apps that got through a wall that stops a lot of solo developers cold, using nothing but reciprocity and a refusal to let it quietly become a paid transaction like most of the alternatives I looked at before building this.
If you've shipped through a closed testing requirement — Play Store or anywhere else — using some kind of swap arrangement, formal or informal, I'd genuinely like to hear what actually worked versus what just technically satisfied the number on paper.
About
I hit Google Play's 12-tester/14-day closed testing wall myself when shipping my own Android app — no existing audience, no easy way to find 12 real people willing to install and actually use it for two straight weeks.

5 Comments
117 completed campaigns plus developers referring others is strong evidence that the reciprocity loop works. The harder question seems to be whether the value is the testing itself or simply clearing Google’s requirement—do repeat users come back when they no longer have an immediate 12/14 wall to clear?
Honest answer: mostly the wall. But it repeats — most devs on PeerPlay publish more than one app, so they're back for the next release rather than staying for the testing itself.
The harder side is testers. Nobody tests out of enthusiasm, so I'm moving toward paid testing to keep them around once their own 12/14 is cleared. That's the part I'm still working out.
That repeat-release behavior is a strong signal. I’d be interested in digging into the paid tester side too. If you’re open to it, what’s the best email to reach you on?
Sure — vmzavas@gmail . Happy to go into the paid tester side in more detail there.
Thanks! I’ve just sent it over.
Looking forward to hearing your thoughts whenever you have a chance.