Başar BallıözProduct Engineer
← All posts

Google Play's 12 testers, 14 days rule

With a new personal developer account you cannot simply publish to everyone on Google Play: you have to pass a closed testing requirement first. I read the rule line by line while preparing Tibblo's Android release. Here is what you need to know.

By Başar Ballıöz · · 3 min read

The rule in one sentence

If your Play Console account is a personal account created after November 13, 2023, you must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days before you can release to production. Until you meet it, production and pre-registration stay locked.

The official wording is on Google's help page, App testing requirements for new personal developer accounts. Rules change, so read that page once more before you apply.

Who it covers, and who it does not

  • Covered: personal developer accounts created after November 13, 2023.
  • Not covered: accounts created before that date.
  • Organization accounts: Google's page only talks about personal accounts. Opening an organization account comes with its own steps, such as a D-U-N-S number, so think about which type actually fits you before switching just to avoid this rule.

One point is unclear: Google's page does not say outright whether the requirement applies to every new app or once per account. It talks about running "a closed test for their app", so I plan as if each app needs its own test.

How the 14-day clock works

This is the part people get wrong most often. The requirement is measured at the moment you apply:

  • At least 12 people must be opted in to your closed test when you apply.
  • They must have been opted in continuously for the preceding 14 days.
  • Someone who opts in and leaves before 14 days does not count. Someone who leaves and rejoins needs 14 consecutive days again.

In practice: start with exactly 12 people and one of them leaves on day 10, and your clock has effectively restarted. Starting with 15 to 20 people, and telling everyone to stay in for at least 14 days, is the safe way.

Before the test starts

  1. Internal testing first. The internal testing track has no requirements. Add yourself as a tester and make sure installing, signing and any purchase flows work.
  2. Finish the app setup. Closed testing needs the Play Console app setup done: content rating, target audience, the Data safety form and a privacy policy link.
  3. Give review a test login if needed. If your app requires signing in, enter working test credentials in Play Console.
  4. Pick real people as testers. Friends, family, colleagues, volunteers from your app's audience. Each needs an Android phone and the Google account they will test with.

During the test

Google looks at engagement, not only the head count: the application asks whether testers used your app's features and whether their use matched what you expect in production. With too little engagement you may be asked to keep testing.

  • Give testers a short task list on day one: install this, try that, open this screen.
  • Collect feedback in one place: a form, a group chat or Play's private feedback.
  • Ship at least one update during the test, based on what testers told you. The form asks what you changed after testing.
  • Keep short notes on who said what and what you fixed. They make the application much easier to write.

I would not use paid "12 testers" services. Google evaluates engagement, policy compliance is always your responsibility, and a test you cannot describe honestly in the form does not help you.

Applying for production access

Once you meet the requirement, an option to apply for production appears on the Play Console dashboard. The form has three parts:

  • About your closed test: how easy it was to recruit testers, whether they used your features, and what feedback you collected and how.
  • About your app or game: target audience, the value it offers, and an estimated install range for the first year. Google says these answers are not shown publicly and do not affect eligibility.
  • About production readiness: what you changed after the test and how you decided the app was ready.

Google says review usually takes seven days or less. Plan for it: even in the best case, count on close to three weeks from first upload to public release.

A sample timeline

  1. Week 1: internal testing, finishing the app setup, building the tester list.
  2. Weeks 2–3: the closed test runs for at least 14 days, with one update in the middle.
  3. Week 4: application and review.

It helps to treat this period as a free beta rather than an obstacle. For the first time, people other than you are using the app, and every place they get stuck is something you can fix before it turns into a store review.

More posts

Godot on iOS: from an uneven 60 fps to 120 Hz with MetalA Godot 4 game stuck near 60 fps on an iPhone 14 Pro with a main thread busy only 4 ms a frame. How a phone bench and Instruments found the cause, and how switching iOS to Metal gave 119 fps. Quest pacing: measuring where a 150-level game goes flatHow I measured the story pacing of Tibblo's 763-day road from level 1 to 150, found where it went flat after level 40, and fixed it with three-step arcs, a daily limit and a 'Last time…' card.