117 developers have shipped through my reciprocal testing app — some of what they said surprised me

One developer left me a note saying he'd sent roughly ten other people to the app. I never asked him to. That's the line I keep coming back to, and I'll explain why below.
Some context first. 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 PeerPlay — 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. Before writing this I went back through every completion note developers left, because I wanted to know honestly whether this was working or whether people were just leaving the moment they technically hit day 14.
Here's the note I opened with, in full:
"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."
The referrals are the part that matters, not the thanks. 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 Google asks for but not the actual point of testing — a gap I think about constantly, because the 12/14 rule checks a headcount, not whether anyone 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 developer's account got suspended mid-test, and he still came back to say the testers had caught a real bug before the suspension happened.
And one that's basically a review of the exact mechanic the whole product bets on:
"Got testers very fast cause i also tested their apps and all testers were active."
People who reciprocate immediately get reciprocated immediately. The ones who treat it as a one-way ask don't.
What I didn't expect: how many notes read like someone surprised that a free system with no payment and no account-selling actually held together. A handful compared 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. Testers no-show. Developers quit mid-campaign — there's a whole mechanic in the app now (a quit counter, visible but not punitive) that exists specifically because that pattern showed up early and often. Ghosting is the default failure mode of any exchange system, and I spent more engineering time on anti-ghosting logic than on almost anything else.
I'll add the uncomfortable part too, since I'm being honest about the rest: right now there are zero active campaigns. The network only has value when campaigns are running, and demand is lumpy in a way I haven't solved. That's the actual problem I'm working on, not the testing experience itself.
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 like to hear what actually worked versus what just satisfied the number on paper.
PeerPlay is here if you're staring at the same wall: https://peerplay.vmcreate.rs
— Viktor Malnar