How apps reach 12 opted-in Play testers, and how well it worked

Finding

The approach with a measured result on our own Play account is this: put every admitted tester into the track's Google Group, so Google mails each of them the opt-in link. It cost nothing, and the app was approved one day after it applied. Outside our account, the reports with numbers come from people who sell testers. They agree on one thing, which is the main way to fail: testers who stop being opted in before day 14, which restarts the clock.

Proof

On our own Play account. Another app went through the same gate. Its tester notes and its ops record, read 2026-11-06:

Date	What happened	Opted in
2026-09-29	30 addresses admitted by email list; most never opened the link	5
2026-09-29	a public Google Group set as the track's tester list, posted to LinkedIn and X	—
2026-10-04	all 26 other admitted addresses added to the group directly; each got Google's mail with the opt-in link	8
2026-10-26	applied for production, form filled in by hand	not read
2026-10-27	production granted, first attempt	—

Its notes say: "The bottleneck is follow-through, not admission … Re-pinging those 25 is cheaper than recruiting 7 strangers." The count when it applied was not written down, so we do not know the exact number that passed.

Imposter today (raw/2026-11-07-play-closed-test-opted-in-count-on-2026-11-07.md). The alpha track already selects testers by one Google Group (ritvi-imposter-testers, per the company accounts page). Opted in: 1 on 2026-10-04, and no reading since. How many people are in the group is not known: only the group's managers can see its members.

Outside our account. Every write-up with numbers comes from a seller. Treat each as a claim:

• A developer who founded a tester service (a paid one, from $49.99) wrote that they restarted the clock three times (dev.to). They recruited exactly 12. One uninstalled on day 8. Three were using second accounts of the same people. One phone stopped being supported. That took about 6 weeks alone, against 19 days with the paid service. Their advice is to "recruit 16-18 people and treat 12 as your floor".
• Tester sellers (Testers Community, Fiverr gigs from about $10–50) advertise approval rates and "guarantees". No independent data backs those claims. Their own blogs say apps are refused for "insufficient engagement" even with 12 or more testers.
• Tester-swap groups (r/TestersCommunity, r/AndroidClosedTesting): each developer tests the other members' apps in return. The posts we saw had no counts we could check.

What it means for Imposter

• Do first: read the opted-in count and the size of the ritvi-imposter-testers group in Play Console and Google Groups (a person has to). If the group has people who have not opted in, add them, or mail them the opt-in link. That is the step that worked on our account.
• Aim for 16 or more, not 12, so that one uninstall does not restart the 14 days. That target comes from a seller, but the rule makes it sensible on its own: the gate fails if the count drops below 12 on any day.
• Who to recruit: people who will play. The form asks whether testers used the app's features. Imposter is played at a table, so one game night with 4–8 Android phones covers several testers at once, and each of them opens the app for real. This is our idea, not a tested result.
• Not recommended:
  • Paid testers. It breaks the "no paid service until a customer pays" rule. It is also the source of the engagement refusals that vendors themselves describe.
  • Switching to an organization account. Google does not confirm it is exempt, it needs a new account, and the D-U-N-S number takes up to 30 days (see play-closed-test-rule).

Searched, found nothing

• A first-hand report with numbers from someone who sells nothing: none found. The Reddit mirror refused to load, and the posts we could read named no figures.
• Independent approval or refusal rates for paid tester services.
• How many people the 2026-10-31 launch posts sent to the tester group (marketing/campaigns.md has no counts).