Google Play Publishing Requirements for New Developers in 2026

Publishing on Google Play used to mean "pay $25, upload an APK, done." In 2026 it is a sequence of gates - account, identity, a second developer-verification layer, build format, listing, a stack of policy declarations, a mandatory closed test, and two separate reviews. Miss one and your app sits in limbo. This guide walks every requirement in the order you actually hit it, flags the 5+ biggest changes for 2025-2026, and is current as of June 24, 2026. Where Google's own pages are vague or lagging, we say so instead of guessing.

The Complete Publishing Sequence (and Why Order Matters)

Google Play approval is not one approval - it is a chain of gates, each of which can hold the whole release. The biggest mistake new developers make is working out of order: building the app first, then discovering identity verification takes days, or finishing the listing only to learn a personal account still has to run a 14-day test. Do the slow, blocking steps early and run the rest in parallel. Here is the order that actually works in 2026:

Step 1: The Developer Account and the $25 Fee

Everything starts with a Google Play Console developer account. You need a Google account with 2-Step Verification enabled, and you must review and accept the Google Play Developer Distribution Agreement and the Play Console Terms of Service during signup.

Payment Methods (This Trips People Up)

The fee must be paid by credit or debit card only. Accepted card types vary by location, but Google's official guidance lists the following - and is explicit that prepaid cards are not accepted:

Personal vs Organization: Same App, Different Paperwork

You choose an account type at signup. Per Google's official help, both types have access to the same functionality and both can monetize through a payments profile. The only real difference is the information Google collects to verify you.

Step 2: Account Identity Verification (and the "5-Day" Myth)

Before you can submit or publish anything, Google verifies who you are at the account level. Personal accounts upload an official government ID; organizations add a D-U-N-S number plus organization documents. Skip or stall on this and the consequences are real: you cannot publish, and unverified developer profiles and their apps can be removed from Google Play and blocked from republishing until verification is complete.

There is a widely repeated number you should ignore. Dozens of third-party blogs claim identity verification "takes up to 5 days." That figure is real, but it is attached to the wrong thing.

One more thing to get straight before the next section: this account-level identity check is not the same as the new Android Developer Verification program. They are two different layers that arrived in 2026, and confusing them is easy. Here is how they differ.

Android Developer Verification: The Biggest 2026 Change

This is the single largest structural change to Android distribution in years, and it is brand new for 2026. Android Developer Verification is a separate program from the account-level identity check you just read about. It requires apps to be registered to a verified developer identity in order to install on certified Android devices - including apps distributed outside Google Play, such as direct APKs and third-party stores. First, see exactly how the two layers differ:

Google's stated rationale, from the March 2026 Android Developers Blog, is security. Their framing is that verification is like "an ID check at the airport" - it confirms the developer's identity but does not review app content. The headline data point they cite:

The Rollout Timeline You Need to Watch

The program opened in March 2026 and ramps up through the year. The date that matters most is September 30, 2026, when enforcement begins in the first four countries.

Two Ways to Register: Full vs Limited Distribution

If you already paid the $25 Play fee, you are covered for full distribution. Brand-new for 2026 is a free tier aimed at students and hobbyists.

Step 3: Build Requirements - App Bundle and Target API

The days of uploading a raw APK are over for new apps. Two build-level requirements decide whether Google Play will even accept your upload: the format and the target API level.

You Must Ship an Android App Bundle (.aab)

Since August 2021, new apps must publish as Android App Bundles - APKs are no longer accepted for new apps. (Existing APK-based apps can keep updating via APK, though migration is recommended.) Alongside this, Play App Signing is required for new apps: Google manages and protects the app signing key, while you keep an upload key to sign the AAB before you upload it.

Target API Level: Current vs Upcoming

This is the one most likely to confuse a first-timer, because the floor is moving. Read both lines carefully:

• In force today (June 2026): new apps and updates must target Android 15 (API 35) or higher. Wear OS, Android TV, and Android Automotive must target Android 14 (API 34) or higher. Existing apps must target at least API 34 to stay discoverable to new users on newer devices.
• From Aug 31, 2026: new apps and updates must target Android 16 (API 36) or higher.

Step 4: Store Listing and Assets

Your store listing is what users (and reviewers) see first, and it has hard technical limits. Get the specs wrong and you cannot publish; get the content wrong and you get rejected. Here are the exact 2026 requirements:

Click to enlarge

The Icon Change Everyone Misses: 30% Corner Radius

New in 2026, per Google's official icon design specifications page (last updated June 15, 2026): you upload a full square icon and "Google Play dynamically handles masking. Radius will be equivalent to 30% of icon size." In plain terms, Google rounds the corners for you - quite aggressively. If your logo or text sits near a corner, it gets clipped. Keep key elements inside a roughly 15 to 18% safe zone.

A preview video is optional - use a public or unlisted (not private) YouTube link, with ads and monetization disabled. Supported screenshot device types span phones, 7" and 10" tablets, Chromebooks, Android TV, Wear OS, Android Automotive, and Android XR.

Metadata Rules That Get Listings Rejected

Google's listing best-practices are strict about promotional language. Keep your title, icon, developer name, and short description clean:

Step 5: App Content and Policy Declarations

This is the section first-timers underestimate. The "App content" area of Play Console is a stack of mandatory declarations, and incomplete or inaccurate answers are one of the most common reasons a launch stalls or an account gets flagged. Here are the seven you will most often touch:

Click to enlarge

Category-Specific Declarations (Know If One Applies to You)

Depending on what your app does, you may hit additional declarations. The notable 2026 ones:

• Health apps: the Health Content and Services policy adds medical-device labeling, a disclaimer requirement for non-regulated health apps, migration of health apps to a verified organization account by January 28, 2026, and granular Android 16 health permissions.
• AI-Generated Content policy: generative-AI apps must prevent offensive output, with stricter labeling and moderation since January 2025.
• Photo and Video Permissions policy (actively enforced): request broad photo and video access only when your core feature genuinely needs it - otherwise use the system photo picker. Updated Location permission rules apply as well. A separate Contacts permissions policy follows later, enforced October 28, 2026 and only for apps targeting API 37 or higher.
• High-risk Permissions Declaration Form: required for sensitive access such as SMS or Call Log, plus the Advertising ID declaration.
• Other categories: News & Magazines, Financial Services, Government apps (organization accounts only), and COVID-19 contact-tracing or status declarations.

Step 6: Closed Testing - 12 Testers for 14 Days

For most new developers, this is the wall. Per Google's official policy, a personal account created after November 13, 2023 must run a closed test with a minimum of 12 testers opted in for at least the last 14 continuous days before applying for production access. Organization accounts are exempt, and so are accounts created before that date.

If you have read that the number is 20, that is outdated. Per the Android Developers Blog: "starting today, we're requiring 12 instead of 20 testers for personal developer accounts." The reduction took effect December 11, 2024, keeping the same 14-day duration, after feedback that 20 testers was tough for smaller developers.

Click to enlarge

The Three Testing Tracks (Only One Counts)

Google offers three tracks, and new developers constantly confuse them. Internal testing feels like the obvious quick option, but it does not satisfy the requirement. Only closed testing does.

At the production application, Google evaluates two things: your tester count (at least 12) and your tester engagement. Their own examples of why they require continued testing include "not having 12 testers opted-in to your closed test, or your testers not being engaged with your app during your closed test." In other words, 12 names on a list is not enough - those testers have to actually use the app.

The Most Effective Way to Pass: Real, Opted-In Testers

Every other requirement in this guide is something you control directly. This one needs 12 real people on real Android devices, opted in and active for 14 unbroken days - which is exactly where solo developers stall. The dependable way to clear it is to bring in real testers who are guaranteed to show up and stay active.

Step 7: The Production Access Questionnaire

Once you meet the closed-testing criteria, a personal account does not flip straight to production - you click "Apply for production" on the Dashboard and answer a questionnaire. You will see this described online as a "10-question form." Ignore that framing: Google updates the wording, and the reliable way to understand it is as three sections, not a fixed question count.

Review and the Real End-to-End Timeline

There are actually two reviews near the finish line: the production-access review after your questionnaire, and the final app review of the release itself. Google processes standard reviews "as soon as possible," but warns that "certain apps may be subject to extended reviews, which may result in review times of up to 7 days or longer in exceptional cases." Apps targeting children, or those that submitted inaccurate target-audience answers, tend to get the more thorough look.

So how long does the whole thing really take for a brand-new personal account? Here is the realistic stacked timeline, with the overlaps that smart developers exploit:

What Actually Delays First-Timers

The total balloons when one of these hits. Almost all are avoidable:

• Incomplete or slow identity verification - started too late, blocking everything else.
• Weak or missing Data safety declarations - the form is mandatory on testing tracks too.
• Invalid reviewer login credentials in App access - the reviewer cannot get in, so they reject.
• Store listing or screenshots that do not match the real app's functionality.
• Slow tester recruitment or low engagement during the 14-day closed test.
• Vague production-access answers that read as generic and trigger "more testing required."

2025-2026 Changes Recap (Quick Reference)

If you only skim one section, make it this one. These are the changes that catch developers who learned the process a year or two ago:

Watch: Google's Official Policy Update (PolicyBytes, April 2026)

Google's Developer Experience team breaks down recent policy changes in its PolicyBytes series, and the April 2026 episode is the official source for several items above - two brand-new policies (Contacts permissions and Account transfers) and two clarifications (age-restricted content and location permissions). Here is the video, with a plain-English breakdown underneath.

Where PrimeTestLab Fits Into All This

Look back at the seven steps. Six of them are paperwork and engineering you control: the account, identity, the build, the listing, the declarations, and the questionnaire. One is fundamentally different - it needs 12 real people on real Android devices, opted in and genuinely active for 14 unbroken days. That single step is where most solo developers stall, and it is exactly what PrimeTestLab handles.

You share your closed testing opt-in link. We handle invitation, opt-in verification, daily engagement monitoring, and full 14-day retention, so one tester dropping out never breaks your streak and resets the clock. 4,500+ apps and counting, at a 99.9% first-attempt success rate across 120+ countries.

Current Packages

Frequently Asked Questions

Bottom Line