Guides / App development
Google Play's 12-tester rule, and how to get around it
If you created a personal Google Play developer account after 13 November 2023, you cannot publish an app to the public straight away. Google requires a closed test with at least 12 testers who stay opted in for 14 days in a row before you can apply for production access. That is hard to arrange when you are starting out. The legitimate way around it is an organisation account, which is not subject to the testing rule but must provide a D-U-N-S number. That is the route we took.
- New personal developer accounts must run a closed test with at least 12 testers for 14 days in a row before they can publish
- Organisation accounts are not subject to the testing rule, but need a D-U-N-S number, which is free
- We registered as a business and published straight to production
What is Google Play's 12-tester rule?
It is a testing requirement for new personal developer accounts. Google's Play Console Help states it in one sentence:
Developers with personal accounts created after November 13, 2023, must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days.
Only after that can you apply for production access, which is what lets you publish to everyone on Google Play.
Older articles say 20 testers, which was the original figure. Google's current help page says 12. Always check the page itself, because the number has changed before.
Who does the rule apply to?
| Account | Does the closed test apply? |
|---|---|
| Personal account created after 13 November 2023 | Yes |
| Personal account created on or before that date | No |
| Organisation account | No |
The requirement is written for personal accounts. Google's stated purpose is that developers test their apps before those apps are eligible for distribution on Google Play.
What exactly counts towards the 14 days?
The details are where people come unstuck. According to Google's help page:
- The 12 testers must be opted in when you apply for production access, and must have been opted in continuously for the preceding 14 days.
- A tester who joins for a few days and then opts out does not count towards the requirement.
- It has to be a closed test. Internal testing is optional and does not count, and open testing only becomes available after you have production access.
- When you apply, Google asks questions about your test and your app, and reviews the answers.
So 12 people on day one is not enough if two of them leave on day five. In practice you want a few more than 12, and people who will actually leave the app installed.
Why is the rule hard for a solo developer?
Because 12 people willing to install an unfinished app, with a Google account each, and leave it alone for a fortnight, is a lot to ask of your friends.
It is very hard to arrange when you are starting out, unless your friends are all developers swapping favours. Many of the people around a new developer use iPhones. And because the 12 have to be opted in continuously, one person dropping out can cost you days.
This is why you see a small industry of tester-swap groups and paid tester services. We would be wary of the paid ones. Google reviews your answers about how the test went, and a dozen strangers who never opened the app give you nothing true to say.
How do you get around the 12-tester rule?
By not having a personal account. Organisation accounts are not subject to the testing requirement, because it is written for personal accounts.
That is what we did. Registering as a business let us publish straight to production.
Have a registered business
A company or other legal entity, with its legal name and address.
Get a D-U-N-S number
Request one from Dun & Bradstreet. Google says applying is free.
Create an organisation account
In Play Console, choose the organisation account type and enter the number, along with the organisation's address, phone number and website.
Verify and publish
Once Google has verified the account, you can publish without the closed test.
It is not a loophole. It is the account type Google intends for businesses, and it comes with obligations of its own.
What is a D-U-N-S number, and what does it cost?
A D-U-N-S number is a nine-digit identifier that Dun & Bradstreet assigns to a business. Google uses it to verify that an organisation is real. Google's help page says: "To create a developer account for an organization, you must provide a D-U-N-S number," and adds that applying for one through Dun & Bradstreet "is a completely free process".
Two practical points. The legal name and address in your developer account must match Dun & Bradstreet's record, so check the record before you apply. And getting a number can take a while, so request it before the app is finished, not the week you want to launch.
Apple also asks organisations enrolling in its developer programme for a D-U-N-S number, so the same number serves both stores.
What are the trade-offs of an organisation account?
| Personal account | Organisation account | |
|---|---|---|
| Closed test before publishing | 12 testers for 14 days | Not required |
| D-U-N-S number | Not needed | Required |
| Who it is for | An individual | A registered business |
| Shown on Google Play | Legal name, country and developer email | Legal name, D-U-N-S number, legal address, email and phone number |
| Registration fee | US$25, one-time | US$25, one-time |
The line that surprises people is what is displayed. Google says that for organisations it shows your legal name, D-U-N-S number, legal address, developer email address and developer phone number on Google Play. If your business is registered at your home, think about that first.
If you are building an app for a business you already run, an organisation account is almost certainly the right type anyway. If you are an individual with a hobby app, running the closed test properly may be simpler than forming a company.
How do you run the closed test properly if you have to?
- Recruit more than 12 testers, so one person leaving does not drop you below the minimum.
- Ask people with Android phones first. iPhone users cannot help.
- Tell testers plainly: stay opted in for the full 14 days.
- Give them something to do, and collect their feedback.
- Fix what they find and release an update during the test.
- Keep notes. Google asks about the test when you apply for production access.
Which apps of ours are on Google Play? HostMaster, Boxerium and Singium are on both stores. Hoopium, Quizerium and Hockeyium are iPhone-only for now. For the Apple side, see getting past App Review.



Sources
- Google Play Console Help: App testing requirements for new personal developer accounts
- Google Play Console Help: Choose a developer account type
- Google Play Console Help: Required information to create a Play Console developer account
- Google Play Console Help: Get started with Play Console
- Apple Developer Help: Program enrollment