Showing posts with label 12 testers for 14 days. Show all posts
Showing posts with label 12 testers for 14 days. Show all posts

Thursday, 5 November 2026

Personal vs Organization Google Play Account: 12-Tester Rule

Personal vs Organization Google Play Account: Does the 12-Tester Rule Apply?

Updated November 2026 · 6 min read

The 12 testers for 14 days closed testing rule applies to personal developer accounts created after 13 November 2023. Organization accounts, and personal accounts created before that date, are exempt. But an organization account is not a shortcut for everyone: it requires a real registered business and identity verification.

Quick comparison

 

Personal account

Organization account

Closed test (12 testers, 14 days)

Required if created after 13 Nov 2023

Not required

Who it is for

Individuals, hobbyists, freelancers

Registered companies, agencies, studios

Verification

Personal ID and contact verification

Business details, D-U-N-S number, website, and more

Setup time

Usually quick

Can take days or weeks

Registration fee

One-time Google fee, same for both

One-time Google fee, same for both

Name shown on Play Store

Your name or developer name

Your legal organization name

When a personal account makes sense

•         You are a solo developer or student.

•         You do not have a registered company.

•         You can spend 14 days on closed testing, or buy testers to fill the 12 spots.

When an organization account makes sense

•         You already own a registered business with a D-U-N-S number and a company website.

•         You publish many apps for clients and want to skip the test each time.

•         You want your company name on the Play Store listing.

Do not register a fake company

Google verifies business details. Using inaccurate information can lead to rejection or a suspended account, which is far more expensive than running a 14-day test. Only choose an organization account if you truly operate as an organization.

Can I switch later?

Apps can usually be transferred between developer accounts, but conditions apply and Google updates the process. Check Google Play Console Help before relying on this.

What should you do?

1.       If you own a registered business: use an organization account.

2.       If you are an individual: stay on a personal account and plan for the 14-day closed test.

3.       If you are short of testers: use friends, communities, or a trusted [closed testing service]. Make sure testers are real, as we explain in [real vs fake Android testers].

FAQ

Is the 12-tester rule the same for every app? It applies per app on an affected personal account until production access is granted.

Was it 20 testers before? Yes. It launched at 20 and was lowered to 12 in December 2024.

Do I need a D-U-N-S number for a personal account? No. That is for organization accounts.

Wednesday, 4 November 2026

Set Up Closed Testing in Google Play Console (Step by Step)

How to Set Up Closed Testing in Google Play Console (Step by Step)

Updated November 2026 · 8 min read

To set up closed testing, open your app in Play Console, go to Test and release → Testing → Closed testing, create a track, add testers by email list, upload a signed release, send it for review, then share the opt-in link. If your personal developer account was created after 13 November 2023, you need at least 12 testers opted in for 14 continuous days before you can apply for production access.

Menu names in Play Console change from time to time, so follow the idea even if a label looks slightly different.

Before you start

•         A signed Android App Bundle (.aab) of your app.

•         A store listing, privacy policy URL, and Data safety and content rating forms started.

•         A list of real people with Android phones and Gmail or Google accounts. Aim for 15–20, because some will drop out.

Step 1: Open the closed testing page

In Play Console select your app, then choose Test and release → Testing → Closed testing. Internal testing will not count toward production access, so make sure you are on the closed track.

Step 2: Create a track

Click Create track, give it a clear name such as “Main closed test”, and continue.

Step 3: Add testers

Open the Testers tab and create an email list. Paste each tester’s Google account email, one per line or comma separated, and save the list. You can also use a Google Group. Each tester must use the same Google account on their phone that you add here.

Step 4: Choose countries

In the Countries/regions tab choose where testers can access the test. If your testers live in several countries, add all of them.

Step 5: Create the release

Click Create new release, upload your signed .aab, name the release, and add short release notes such as “First closed test build”.

Step 6: Send it for review

Save, review, and roll out to closed testing. Google may review closed testing releases first, which can take from a few hours to a few days. Testers can install only after it is approved.

Step 7: Copy and share the opt-in link

In the Testers tab copy the opt-in link (“How testers join”). Send it to every tester with these instructions:

1.       Open the link while signed in to the Google account you gave us.

2.       Tap Become a tester.

3.       Install the app from the Play Store link that appears.

4.       Open the app and use it for a few minutes. Keep it installed for at least 14 days.

Step 8: Watch the count and apply on day 15

In the Dashboard you will see the closed test progress. When 12 testers have stayed opted in for 14 continuous days, the Apply for production option appears. Answer the questions honestly and in detail. Our [production access questionnaire guide] explains what Google asks.

Five mistakes that break the 14 days

1.       Testers installed the app without tapping Become a tester.

2.       The tester’s email in your list is not the account on their phone.

3.       Testers uninstalled before day 14. Replace them early.

4.       Using the internal track instead of closed testing.

5.       Testers installed but never opened the app, so engagement is low.

FAQ

How long does closed testing take? The test itself is 14 continuous days. Allow another few days for review and the production access application, so plan about three weeks overall.

Can testers use the same email twice? No. Use 12 different real Google accounts.

Do I need to repeat this for every app? Yes, for each new app on an affected personal account until the account has production access.

Don’t have 12 testers? You can ask friends, developer communities, or use a [Google Play closed testing service] that supplies real testers who opt in through your own link.