Google has made publishing harder since 2023. If you haven't followed the updates, publishing an app in 2026 looks very different from two years ago. This guide explains the most important changes and what they mean for your launch.
Note on Scope
This guide covers the rules that matter most for new apps and production access. It doesn't cover every Google Play update, only the changes that affect whether you can publish a new app.
The Closed Testing Requirement
The biggest change for new developers started in November 2023 and is still in place in 2026. If you created a personal Google Play Developer account after that date, you must finish a closed test before you can apply for production access.
The rule: at least 12 testers must stay opted in to your closed track for 14 days in a row.
Google says it made this change to cut down on low-quality apps. The 14-day rule slows down low-effort submissions and gives serious developers a clear path.
What "Active" Actually Means
Google doesn't say exactly what counts as "active." Many developers report that testers need to really use the app, not just install it. Testers who install the app and never open it are unlikely to help your application.
The Production Access Questionnaire
The production access questions have grown. Early versions asked simple things like app category and audience. The current form asks more detailed questions about:
- Your app's core functionality and monetisation model
- The specific devices and Android versions your testers used
- The geographic distribution of your tester base
- How you recruited and verified your testers
- Any previous production access rejections and their reasons
Reviewer Red Flags
Generic, copy-paste answers look bad to reviewers. If your description of your testing sounds copied from a forum post instead of what you really did, expect extra questions or a rejection.
Improved Emulator and Device Farm Detection
Google has gotten better at spotting fake testing. A few years ago, some emulator-based services may have slipped through. That gap is now much smaller.
Google Play appears to collect more device signals than before, and it likely compares test activity across many apps. Automated systems help tell real testers from scripts and virtual devices.
What this means: a service that used emulators or shared device farms in 2023 and got away with it probably can't do that reliably today. Using one is riskier now than ever.
Data Safety Requirements
Google has tightened the Data Safety section in Play Console. Apps that collect any user data must now:
- List every type of data they collect in the Data Safety form, accurately
- Give a privacy policy link that really describes the data practices they declared
- Update the Data Safety section within a set time when their practices change
Reviewers now compare your Data Safety answers with your app's real permissions and third-party SDKs. A mismatch is a common reason for rejection that has nothing to do with testing. Make sure your Data Safety form is accurate before you apply for production access.
What This Means for Your Launch Strategy
Together, these changes mean you need to plan differently than you did before 2023:
- Build your launch timeline around the 14 days. Factor the testing period into your go-to-market plan from the beginning, not as an afterthought.
- Use a verified, documented testing service. Testing you can't prove (friends who may not have used the app, or cheap online services) creates risk at the questionnaire stage, even if the test "passes" in the console.
- Finish your Data Safety form before applying. Being rejected over a Data Safety mismatch after you've done the full 14-day test wastes time and hurts your credibility with reviewers.
- Answer the questionnaire in detail. Describe your real testers, their real devices, and what you really did. Vague answers get rejected in 2026.
Source: Google Play Console Help: App testing requirements for new personal developer accounts.
Frequently Asked Questions
Does the 14-day requirement apply to organisation accounts?
Not in the same way. The strict rule is for new personal developer accounts. Organization accounts follow a different review process that is still strict. Check your Play Console under Developer account type to see which applies to you.
What changed in the production access questionnaire?
Google expanded the questionnaire a lot. Reviewers now ask how you tested, which devices were used, where your testers are, and what your app does, in much more detail. Vague or copy-paste answers are more likely to be rejected now than before.
Is the 14-day policy likely to change in 2026?
As of August 2026, Google hasn't announced any change to the 14-day rule. There's talk in the community about relaxing it for some app categories, but nothing official. The rule is still fully in effect for new personal accounts.