Google Play Publishing Requirements for New Accounts

Publishing on Google Play with a personal developer account created after 13 November 2023 means clearing several gates, and they run on different clocks. The one everybody talks about is closed testing — at least 12 testers opted in continuously for the 14 days preceding your application. The one that catches people by surprise is device verification, which has been required for new personal accounts since early 2024.

None of these gates substitutes for another. Satisfying the testing requirement does not verify your device, and verifying your device does not unlock production. Treat them as parallel tracks with their own prerequisites rather than a single queue.

The gates, in the order they tend to bite

Gate one: device verification

Google's documentation states that developers with new personal accounts are required to verify they have access to a real Android mobile device using the Play Console mobile app before they can make their app available on Google Play. It was introduced from early 2024 as a trust and safety measure, on the reasoning that developers who can access a device are able to properly test their apps.

The steps are short:

1. Log into Play Console on the web as the account owner.
2. Go to the Home page.
3. Find the task named Verify that you have access to an Android mobile device and click View details.
4. Scan the QR code to install the Play Console mobile app on the device you will verify with.
5. Open the app, log in as the account owner, and select your developer account.
6. Tap Verify and follow the on-screen instructions.

Once complete, the task disappears from the Home page. Google's FAQ covers the natural questions — which devices qualify, whether a device used for another account can be reused, and how long verification takes — so check there rather than guessing.

The practical implication: if you do not own or have access to a physical Android device, this gate is a genuine blocker, and it is worth knowing before you spend two weeks on a closed test.

Gate two: app setup

A closed test cannot start until app setup is complete. Google states you can start a closed test after completing your app setup, and that internal testing is the track available before that.

Which means the setup items are on your critical path even though they seem like paperwork:

• Store listing — the app's public-facing presentation, needed because closed testers still see it.
• Content rating — Google lists app targeting and content rating accuracy as something reviewers check, and an inaccurate rating is a policy issue rather than a formality.
• Privacy policy and data safety declarations — required for the listing, and a common cause of listing approval delays.
• Target API level — Google maintains a separate requirement here that has its own deadline cycle. Check the current requirement rather than relying on a blog post.

Getting these done before recruitment starts is the single easiest way to shorten your timeline. Setup work you do while waiting for testers is setup work that is not delaying you.

Gate three: closed testing

The requirement for personal accounts created on or after 13 November 2023: at least 12 testers opted in continuously for the preceding 14 days when you apply for production access. The minimum dropped from 20 to 12 on 11 December 2024.

Two operational notes that matter more than the number itself:

• Opted in, not invited. Testers join by opening the opt-in link. The link only displays once the app status is Published, and Google documents that it can take several hours to become available after your first test release.
• Continuously. It is a state you hold, not a total you accumulate. A day below 12 breaks the run.

Recruit 15-16 rather than 12. Testers dropping below the minimum accounts for roughly 40% of the rejections in OnTesters' own campaign data across 1,500+ analyzed campaigns — our figures, not Google's.

Gate four: production access review

Meeting the criteria unlocks the application. It does not approve the app.

Google describes the application as three sections — About your closed test, About your app or game, and About your production readiness — and states that review usually takes seven days or less, though it can take longer. You must summarise your testing feedback as part of it.

Google also notes that Pre-registration and the Production track remain disabled until the testing requirements are met, so there is no ambiguity about where you stand before you apply.

Gate five: policy compliance

Google's guidance is blunt about this one: it is your responsibility to ensure the app complies with Play policies before submitting, and submitting non-compliant apps expecting reviewers to identify the issues leads to rejections, review delays, and lengthier appeals. Review is not a troubleshooting step.

The areas Google names:

If your app requires login and reviewers cannot get in, nothing else you did matters. Verify the credentials yourself on a device that has never seen your app.

A realistic schedule for a new personal account

1. Day 0: Complete device verification. It takes minutes and it is a hard gate.
2. Days 0-2: Finish app setup — listing, content rating, privacy policy, data safety, target API level.
3. Days 1-7: Recruit 15-16 testers in parallel. Do not wait for setup to finish.
4. Day 7: Publish the closed release, confirm the opt-in link resolves, send it out.
5. Days 7-21: Hold 15-16 opted in. Ship two or more updates. Collect feedback continuously.
6. Day 21: Confirm 14 continuous days at 12 or more. Summarise feedback. Apply.
7. Days 21-28: Review, expected within seven days and possibly longer.

Common sequencing mistakes

• Starting recruitment before app setup is done. Closed testing unlocks after setup, so testers who arrive early have nowhere to opt in.
• Sending the opt-in link immediately after publishing. Google documents a several-hour delay; a link that does not resolve burns goodwill.
• Discovering device verification last. It is one tap in the Play Console app and it can block your release.
• Assuming the review is a formality. It is a review, and the application asks questions you need material to answer.
• Leaving policy checks until after approval. Google states clearly that policy review is not a troubleshooting step.

Sequencing the gates so nothing blocks anything else

Most delays on a new account come from doing the right things in the wrong order. The gates have dependencies, and two of them are commonly done backwards.

1. Device verification first. It takes minutes and it gates making your app available on Google Play. There is no reason to discover it later.
2. App setup second, but recruitment in parallel. Closed testing cannot start until setup is complete, which tempts developers to treat recruitment as the next step. It is not — sourcing is the long pole, so start asking people the same week.
3. Publish the closed release, then wait for the link. Google documents a delay of several hours before the opt-in link resolves after your first test release. Sending it early burns goodwill you spent a week building.
4. Hold 14 continuous days at 12 or more. This is the fixed block in the schedule and the one that cannot be compressed.
5. Apply, then wait for review. Google states review usually takes seven days or less, and can occasionally take longer. A launch date booked at day 14 is a launch date one review cycle from slipping.

The two that get done backwards are verification (left until release day) and recruitment (left until setup finishes). Both are cheap to fix and expensive to discover, and the sequencing shows up in the timeline in How Long Does Google Play Closed Testing Take?

Where the requirements interact

The gates are independent in their criteria and dependent in their timing. Understanding which is which saves a surprising amount of frustration.

Two rows reward attention. Policy compliance has no prerequisite and no notification: it is the item you are expected to have handled before submitting, and Google is explicit that review is not a troubleshooting step. And the privacy declarations sit inside app setup, which means a missing policy link can stall your closed test before a single tester has opted in.

What the first month actually looks like

Four weeks is a reasonable expectation for a first-time personal account, and the variance is almost entirely in recruitment and re-runs rather than in anything Google does. If your plan says ten days, the error is in the recruitment row. The channels and their realistic timelines are compared in How to Find Android App Testers for Closed Testing.

Two timelines, side by side

The most useful thing a new developer can see is what a realistic schedule looks like when the gates are sequenced properly, against one where they are discovered as they arrive.

The difference is not effort. Both developers did the same work; one of them did it in a different order. The two changes that produce the sequenced column are starting recruitment while setup is still finishing, and completing device verification before anything else — see How Long Does Google Play Closed Testing Take?

Frequently Asked Questions

What do I need to publish on Google Play with a new personal account?

Closed testing with at least 12 testers opted in continuously for 14 days, device verification confirming access to an Android device, completed app setup including listing, content rating, and privacy declarations, and a production access application that Google reviews.

Do I need a physical Android device to publish?

Google requires developers with new personal accounts to verify access to a real Android mobile device using the Play Console mobile app. That verification is a prerequisite for making your app available on Google Play.

How long does device verification take?

The steps themselves are quick — install the Play Console mobile app, log in as the account owner, select your developer account, and tap Verify. Google's Help Center FAQ addresses device eligibility and timing questions in more detail.

Can I publish without running a closed test?

Not with a personal account created on or after 13 November 2023. Organization accounts are not subject to the closed testing requirement.

Does device verification replace closed testing?

No. They are separate requirements. Device verification confirms you have access to an Android device; closed testing is about real users testing your app for 14 days. See Developer Verification vs Closed Testing on Google Play.

Sources

Google Play Console Help — App testing requirements for new personal developer accounts (testing requirement, application sections, review timing, policy compliance areas, disabled features). Google Play Console Help — Device verification requirements for new developer accounts. Google Play Console Help — Prepare and roll out a release. OnTesters campaign figures are our own.