Google Play’s 12-tester rule, explained

The question appears several times a week on Android forums: “Where do I find 12 testers for 14 days?” It is the step first-time publishers did not know existed until Google’s console told them, and it adds two to three weeks to every first launch. Here is what the rule is, who it hits, and how to make it useful.

1. The rule

Personal developer accounts created after 13 November 2023 must, before they can publish an app publicly:

1. run a closed test (a release only invited people can install) with at least 12 testers,
2. keep those testers opted in continuously for 14 days,
3. then apply for production access, which Google reviews, usually within a few days.

Organisation accounts (registered as a business) are exempt. The count was higher when the rule launched and is 12 now. It applies per account, not per app: once your account has production access, later apps skip the test.

2. What counts

A tester is a Google account that has accepted your invite and installed the test build. Twelve opted-in accounts for fourteen days means fourteen consecutive days with at least twelve opted in. Reports from developers say the clock does not survive a dip below twelve, so treat it as continuous and recruit a margin: twenty is the number that survives two people dropping out and a cousin who never gets round to installing.

3. Recruit without begging

“Test for test” swaps with strangers on forums technically work and teach you nothing. Better sources, in order:

• The people your app is for. If you built it for your club, your staff or your customers, they are your testers, and the test is their first look. This is the whole point: the 14 days are a built-in first-users programme.
• Your own household and friends, with the honest line that they need to install it once and leave it installed.
• The two people who already said “when can I have this?” during the design stage.

Tell everyone the exact ask: accept the invite, install, keep it installed for two weeks, open it when you remember. Nothing else.

4. Use the 14 days

Do not sit out the fortnight. Ship a fix every few days to the closed track; testers get it automatically, and each one is a reason to open the app again. Ask one question each week: what did you expect to happen when you tapped that? By day 14 you have twelve people’s complaints, which is more than most apps have at launch.

5. After the clock

Apply for production access from the console. Google asks about your testing and your plans; answer plainly and with what you learned. Approval has been taking a few days. Then your open or production release goes through Google’s normal review, which for a small app is also days.

So the honest first-launch timeline on Android is: an installable build, two weeks of closed testing, a few days of approvals. Start the account and the identity checks on the day you start designing, because they take days of their own, and have the build ready the moment the account is live.

If you are still before the build, the quickest way to twelve testers is a design they can hold: put the App Builder preview on their phones now, and the same twelve people become the closed test when the build exists.