How to Publish an App on Google Play

Personal vs Organization Accounts

Play Console offers two account types with the same core features. Personal accounts are meant for students, hobbyists and individual developers. Organization accounts are for businesses and require a D-U-N-S number. Google also requires an organization account for certain kinds of apps, including financial products and services, health apps, apps that use the VpnService class and government apps. If a business owns the app, use an organization account so the business is the developer of record and you avoid the personal-account testing gate described below.

Registration costs a one-time 25 USD fee, and Google verifies identity. Expect to supply official documents and to verify a contact email and phone number. Personal accounts must also confirm access to a real Android device through the Play Console mobile app. Plan a few days for verification before your intended launch.

The Closed Testing Requirement

Developers with personal accounts created after November 13, 2023 must run a closed test before they can publish to production. The test needs at least 12 testers who have been opted in continuously for the preceding 14 days. Testers who opt out early do not count, and the clock is about continuous enrollment, so recruit a few more than 12 and keep them engaged. After the test, you apply for production access and answer questions about the test and your app.

Even when the rule does not apply to you, use the testing tracks. The internal track gets a build to your team within minutes, and closed testing with real customers catches device-specific bugs. Android runs on thousands of device models, so a bug that never appears on your phone can appear on a budget handset with less memory.

Technical Rules to Plan Around

• Target API level. Google raises the minimum every year. Starting August 31, 2026, new apps and updates must target Android 16 (API level 36), with Wear OS, Automotive, TV and XR apps on lower thresholds. You can request an extension to November 1, 2026 in Play Console. Existing apps that fall behind remain available to current users but are hidden from new users on newer Android versions.
• App Bundles and signing. New apps must be published as Android App Bundles, and Play App Signing manages your app signing key. Protect your upload key and record who holds it.
• Permissions. Sensitive permissions such as background location, SMS, call log and broad file access require declarations and are restricted to apps that genuinely need them.
• Developer verification. Google's Android developer verification program ties apps to verified developers. Google says it registered almost all Play apps automatically; check the Play Console home page for any app that still needs registering.

If you use a cross-platform framework, confirm it supports the required API level before your release date. A framework upgrade can take longer than the feature work. See React Native vs Flutter for how the two main options handle platform updates.

Data Safety, Content Rating and App Access

The App content page in Play Console collects declarations that reviewers check against the app:

• Data safety: what user data the app collects and shares, why, whether it is encrypted in transit, and whether users can request deletion. It must include data collected by analytics, advertising and crash-reporting SDKs. Inventory your SDKs before filling it in.
• Content rating: a questionnaire that produces ratings for different regions. Answer honestly; misrepresenting content can lead to removal.
• Target audience: if the app appeals to children, the Families policies add requirements for ads, data and content.
• App access: give reviewers working credentials and instructions for any feature behind a login, a paywall or a location check.

Apps that let users create an account also need a way to request account and data deletion, both inside the app and through a web link listed in the Data safety form.

Review, Rollout and the First Month

Google reviews new apps and updates before they go live. Reviews for new developer accounts and new apps can take several days, so do not set a marketing launch date until you are approved. Once approved, use a staged rollout: release to a small percentage of users, watch crash and ANR (app not responding) rates in Android vitals, and increase the percentage when things look stable. You can halt a rollout if something goes wrong.

After launch, the store listing becomes a marketing asset. Test your screenshots and short description with store listing experiments, and read what App Store optimization is for the basics. If you are also shipping on iOS, compare this process with our guide to publishing on the Apple App Store; most teams prepare both listings in parallel.