Do You Need New Testers (and a New 14-Day Test) for Every App?

Production access is per app

Google’s requirement says developers with new personal accounts must run a closed test for their app with at least 12 testers opted in for 14 days before applying for production access for that app. Approval for app A doesn’t unlock production for app B. Every new app on the account goes through its own test and application.

Reusing testers is fine

Nothing in Google’s help says testers must be unique to one app or one developer. A friend who tested your first app can test your second. What matters:

• They opt in to the new app’s closed test using its own opt-in link.
• They stay opted in for 14 consecutive days.
• They actually use the new app, so your application has real evidence.

Practical tips for app #2 and beyond

• Keep a tester list. Save the emails (with consent) of people who were engaged last time, and put them in a Google Group you can attach to any track. See using a Google Group for testers.
• Don’t overload the same people. Testing two of your apps at once is fine. Five at once usually means none get real use. See one person testing several apps.
• Space out launches. Running tests back to back means you can reuse your engaged testers instead of recruiting from scratch.

Is there a way around it?

Organization accounts aren’t subject to this testing requirement. That’s a legitimate path if you really are a registered business, but it requires a D-U-N-S number and organization verification. See personal vs organization accounts and can you skip the 12 testers requirement.

Frequently asked questions