play-closed-test-how-others-passed

Summary

How others got 12 testers for 14 days, with the numbers found. The one first-hand pass found is another app on the same personal Play account: it went from 5 to 12+ opted-in testers in about four weeks by re-mailing people who were admitted but had never opted in. Public write-ups mostly come from people selling testers, so their numbers are claims.

Built from

• Another app on the same Play account, in its own repo (the company rule keeps product names out of this repo): its tester-recruitment page, release file, tasks.md and commits read on 2026-11-07 local time
• Two more apps on the same account, from their release file, problem pages and raw/
• Web search, sources listed below
• play-closed-test-rule

Body

First-hand: an app on the same account that passed

Date	Opted in	Source
2026-09-29	5 of 30 admitted	its tester-recruitment page, read from the Console
2026-10-04	8	commit "record the closed-test tester count read on 2026-10-04"
2026-10-26	gate met: the Console opened the production application	commit "apply for Play production"; the count was not read that day
by 2026-11-02	production release completed	its release file, from the Play API

What it did:

• Found the real gap. 30 people were admitted by email list, but only 5 had opted in. Its page says re-mailing those 25 is cheaper than finding 7 strangers.
• Moved to a Google Group anyone can join, with no approval, and set the group as the closed track's tester list.
• Added the 26 people from the old email lists to the group on 2026-10-04. Each got a mail with the opt-in link, which was the re-ping.
• Posted the group link on LinkedIn and X, and listed it on the portfolio page.
• Review took 7 days or less (applied 2026-10-26, live by 2026-11-02).

First-hand: two apps on the same account that have not passed

• One had 1 opted in on 2026-10-04. Launch posts went out on 2026-10-31. No count has been read since, and production is still empty.
• One had 5 opted in on 2026-10-04 and no later count. Production is still empty.
• Lesson: a public post alone did not move these. Neither has a later count, so it is not proven either way.

Public sources (mostly claims)

• Tester swaps break. A founder on Indie Hackers did 3 swaps and "never hit 12 continuously", because people dropped out. He now sells a tester service, so this is a claim. https://www.indiehackers.com/product/ontest
• Tester communities and paid testers (Fiverr gigs, testerscommunity.com, ontest.app) promise 12 testers and "guaranteed" access. These are sellers' claims. Google's application asks whether use "matched expected production user behavior", so testers who never really play are a risk. One dev.to post says reviewers saw 8 of 12 testers stop after day 4 and refused the app (also from a tester-selling account). https://dev.to/testerscommunity/google-play-rejected-my-app-after-14-days-of-testing-here-is-what-i-did-wrong-3c21
• Common advice: recruit from friends and work networks (Google's own page says this too), aim for more than 12, and keep testers playing for the whole 14 days.

Searched and found nothing

• Independent numbers on how often production applications are refused, or how long the gate takes on average. Only seller blogs give numbers.
• A Google announcement of the 20-to-12 change.
• A first-hand Reddit thread; the search returned only mirrors and seller posts.

Chess today

• Admission is the same as the app that passed: the alpha track admits the ritvi-chess-testers Google Group (IDEA-0002). The group's about page answers HTTP 200 on 2026-11-07; whether anyone can join without approval was not checked, because that needs a signed-in browser.
• The opted-in count and the group's member count are not known (needs Play Console; T033).
• Alpha may still serve 1.0.0 until Google approves the 2.0.0 rollout (T042). Testers who play an old build give weaker feedback.