PeerPlay
Seven VIP campaigns are running on PeerPlay this week. These are paid Google Play closed tests: a developer pays for a package of tester slots, and those testers open the app every day for 14 days while the developer works toward production access.
This morning, October 28, 2026, I took screenshots of my Discovery screen, where six of them sit next to each other. I won't name the apps or the testers. But the screen says a lot about what really happens during the 14 days, so here is what I see.
The six campaigns on one screen
A sudoku puzzle game, launched six days ago: full, 20 of 20 testers. One piece of feedback so far.
A card games app, launched a week ago: full, 20 of 20. Seven pieces of feedback.
A Halloween-themed game, about two weeks in: full, 20 of 20. Seven pieces of feedback.
A Christmas-themed game from the same developer, launched today: one slot left.
A Spanish learning app, launched two days ago: full, 15 of 15. Two pieces of feedback.
A dating app, launched four days ago: 14 slots still open, nine pieces of feedback, and three issue reports from testers on its card.
Slots fill fast, unless something blocks the door
Most of these campaigns are full, and the newest game filled all but one slot on its first day. When the setup works, getting testers to join is not the hard part.
The dating app is the exception, and its card shows a likely reason. Testers have reported all three issue types PeerPlay lets them send: a Google Group error, a country availability problem and a broken download link. A tester who can't get in doesn't take a slot, and the campaign waits. If your tester count is stuck, check your group settings, your track's countries and your opt-in link before you blame the audience.
What testers actually wrote
The Halloween game is the furthest along, so its feedback shows the whole arc. In order, from the first week:
First, a bug report: "please fix your google group, I am seeing content not available." The first problem was not in the app at all. It was the door to the app.
Then praise, as a star report: "Love Halloween UI."
Then the hard one: most features felt unresponsive, and the tester had to tap several times before anything happened. The same tester followed up two minutes later with a star report: the colour palette is good, but the app needs a tutorial at the start, because it is too confusing.
Then two very different star reports. One said "Best app I ever tried." The other said "consider increasing the ui elements size."
What a developer can take from this
Expect setup problems first. In this campaign the first report was about the Google Group, and on the dating app three reports are about getting in. Test your own opt-in link from a fresh Google account before day one.
The useful feedback is specific. "Best app I ever tried" is nice to read and tells you nothing. "Tap several times before anything happens", "needs a tutorial" and "make the UI elements bigger" are three things a developer can fix and then mention in the production application, where Google asks what you learned from testing.
One tester can give you most of it. The unresponsiveness report and the tutorial suggestion came from the same person, two minutes apart. When a tester writes in detail, reply and ask a follow-up question while they still remember.
One report was about us
Not every piece of feedback is about the app being tested. A few days into the Halloween campaign a tester wrote: "I am testing every day and the system says I didn't reach the goal." That one is about PeerPlay's own day counting, not the developer's app.
I'm leaving it in because it is honest and common. Day counts depend on time zones and on when a test is recorded, and I wrote a whole post after a tester was counted from day 2 because his first test landed just after midnight. If your testers say the count looks wrong, check the boundary before assuming they skipped a day.
I'll come back to these campaigns when they finish and write about how many of them get through Google's production review.
FAQ
How many testers does a paid PeerPlay campaign include?
The campaigns in this post have either 15 or 20 tester slots. Testers open the app every day for the 14-day closed test.
Why would a closed test stay half empty?
Usually because testers can't get in: a Google Group that blocks joining, a track not available in their country, or a broken opt-in link. Fix the setup before recruiting more.
What feedback do closed testers usually give?
In these campaigns: setup problems first, then responsiveness, onboarding confusion and UI size, plus some general praise that is nice but not actionable.
What should I do when a tester gives detailed feedback?
Reply quickly with a follow-up question while they remember the details, fix what you can, and note the change for your production application.