Skip to content
Velloreth
Android Development 8 min read

Publishing to Play Store: A Step-by-Step Guide

A practical walkthrough of shipping an Android app on Google Play — signing, Play Console setup, target API levels, Data safety, and the review process.

By

Publishing an Android app is mostly logistics: the code is done, and what remains is signing, policy paperwork, and a review queue. None of it is hard, but each step has a failure mode that delays release — a missing privacy policy, a Data safety form that does not match the app, a target API level past the deadline. This is the path from a finished build to a live listing, in order.

Before you touch Play Console

Three things to settle in the project first, or the Console will block you later.

Target API level. Google Play requires new apps and updates to target a recent Android version. As of August 31, 2026:

App typeRequired target
New apps and updates (mobile)Android 16 (API 36) or higher
Existing apps, to stay discoverable on newer devicesAndroid 15 (API 35) or higher
Wear OS and Android Automotive OSAndroid 15 (API 35)
Android TV and Android XRAndroid 14 (API 34)

An existing app below the two-year threshold does not disappear — users who already installed it can still use it — but it stops being available to new users on devices running a newer OS than the app targets. Extensions are available through Play Console for apps that need more time; the deadline for the current cycle’s extension window is November 1, 2026.

Signing. Use Android App Bundles (AAB), not APKs, and enroll in Play App Signing. Google manages the app signing key that signs what users install; you sign the upload with your own upload key. Keep the upload key in a keystore you back up — if you lose it, you can request a reset, but the process takes time. The Gradle config looks like:

android {
    signingConfigs {
        create("release") {
            storeFile = file("keystore/release.jks")
            storePassword = System.getenv("KEYSTORE_PASSWORD")
            keyAlias = "release"
            keyPassword = System.getenv("KEY_PASSWORD")
        }
    }
    buildTypes {
        release {
            isMinifyEnabled = true
            signingConfig = signingConfigs.getByName("release")
        }
    }
}

Package name. It is permanent once the first upload is submitted. Choose com.yourdomain.app style — reverse-domain — and never change it. If the app will have a free and paid flavor, they are two different package names.

Play Console account

Register at play.google.com/console. The $25 one-time fee covers an individual or organization account. Certain categories must register as an organization with additional verification:

  • Financial products and services (banking, trading, crypto)
  • Health apps, including medical and human-subjects research
  • Apps approved to use VpnService
  • Government apps

Every developer must complete identity verification — legal name, address, contact email and phone, and a Google payments profile. Verified information is shown on Play to help users trust the developer, so keep it accurate; inconsistent details delay review.

The app in Play Console

Create the app, then work through the requirements in roughly this order — each one gates the next.

1. Store listing

The public face of the app:

  • Title — up to 30 characters, unique, no keyword stuffing.
  • Short description — up to 80 characters; this is what people read first.
  • Full description — up to 4,000 characters; describe what it does, not a wall of keywords.
  • Graphics — feature graphic (1024×500), at least two phone screenshots, plus tablet, Wear, or TV assets if you support those form factors.
  • App category — pick one; it affects discovery and which policies apply (kids categories have extra rules).

Screenshots sell the app more than the description does. Capture the first-run experience, the core flow, and one or two differentiators. If the app supports dark theme or multiple languages, showing them helps.

2. Privacy policy

Required for every app. The policy must be:

  • Hosted at a public, stable URL — not a PDF, not geofenced, not editable after submission in ways that break the link
  • Linked in Play Console and reachable from inside the app (a Settings or About screen)
  • Honest about what the app accesses, collects, uses, and shares — including data collected by third-party SDKs
  • Labeled clearly as a privacy policy

If the app has account creation, Play also requires an in-app way to delete an account, and deletion must actually delete the associated data — not just deactivate.

3. Data safety form

The Data safety section is a structured declaration of data practices, shown on the store listing. It must cover:

  • What data is collected (location, personal info, health, financial, photos, app activity, device IDs — the form walks you through categories)
  • Whether collection is required or optional
  • Whether data is shared with third parties
  • Whether data is encrypted in transit
  • Whether users can request deletion
  • How the data is handled — the same disclosures must appear in the privacy policy

The form applies globally: if any version of the app, anywhere, collects a type of data, you declare it. Third-party SDKs count — analytics, ads, crash reporters, AI integrations. If an SDK collects device identifiers, that is your declaration to make. The Google Play SDK Index lists many providers’ published data-safety guidance; use it, but verify against the SDK’s actual behavior.

An inaccurate Data safety form is a policy violation, and policy violations block releases. If you are unsure about a data type, under-claiming is not safer than over-claiming — accuracy is the requirement.

4. App content and access

Depending on the app, Play asks for more:

  • App access — if the app requires a login, provide review credentials (email/password or a QR code) so testers can sign in. Stale credentials are a common review-delay cause.
  • Content ratings — complete the IARC questionnaire; ratings differ by region.
  • Ads declaration — whether the app contains ads.
  • Target audience — whether the app is directed at children; if so, the Families policy applies, including restrictions on data collection and ads.
  • News policy — if the app is a news app, complete the news declaration.

Closed testing and the install-base requirement

Google Play now requires new personal developer accounts to run a closed test with a minimum number of testers for a continuous period before moving to production. The exact requirement has been in flux; check the current policy in Play Console before planning the timeline. Practically: invite a group of testers (friends, colleagues, a mailing list), have them install from the closed track, and collect feedback for at least a couple of weeks. Even when not required, closed testing is the cheapest place to catch crashes — the Play Console’s crash and ANR dashboards fill with real device data you will not get from your own phone.

Create the release in Testing → Closed testing, upload the AAB, and roll it out to the track. Testers opt in via a link; installs count toward the requirement and give you Android vitals data.

Production release

When the build is ready:

  1. Upload the AAB to a new production release. Play validates the bundle, checks the target API level, and runs policy checks.
  2. Release name and notes — users see these in the Play Store and in in-app update prompts. Keep notes short and user-facing.
  3. Staged rollout — release to a percentage of production users (10%, 20%, 50%, 100%). Watch the crash dashboard for a day or two at each step. A bad build at 100% is a race to roll back; at 10% it is a Tuesday annoyance.
  4. Country targeting — choose where the app is available. A phased geographic rollout works the same way: start with one or two countries, expand when stable.
  5. Submit for review. The button says “Start rollout to production.” Review usually finishes within hours; new accounts and sensitive categories take longer.

After approval, the app is live. The listing updates within a few hours; search indexing takes longer.

After launch: the maintenance loop

Publishing is not the end of the process. The Play Console gives you a loop to run every release:

  • Android vitals — crash rate and ANR rate per version. Google blocks releases that exceed thresholds; fix crashes before they become blocks.
  • Policy status — warnings for data-safety mismatches, permission misuse, and content policy issues. Read these promptly; unresolved warnings can eventually block new submissions.
  • Reviews and ratings — respond to critical reviews; they are free product research.
  • Target API deadlines — Google publishes the next deadline yearly. Budget for the migration early; the work is usually a compileSdk bump plus behavior-change fixes, not a rewrite.
  • In-app updates — the Play Core in-app updates API lets you prompt users to update without leaving the app. For critical fixes, this moves users faster than waiting for organic updates.

A checklist worth keeping

  • Package name final and version code strategy in place
  • AAB build with Play App Signing enrolled; upload key backed up
  • Target API level meets the current deadline
  • Privacy policy at a stable public URL, linked in-app
  • Data safety form accurate, including third-party SDKs
  • Store listing complete with real screenshots
  • Review credentials working
  • Content ratings and target audience set
  • Closed test run with real testers
  • Production release staged, not 100% on day one

None of these steps is technically difficult. The delay in shipping an app to Play is almost always a missing artifact — a policy URL that 404s, a Data safety entry that does not match an analytics SDK, credentials that expired. Work through the checklist before the build is “done,” and release day is a button press instead of a week of back-and-forth with review.

Frequently asked questions

How much does a Play Console account cost?
A one-time $25 registration fee. Organizations — financial services, health, VPN, and government apps — must also provide organizational details including a D-U-N-S number.
How long does review take?
Most submissions are reviewed within hours to a few days. New accounts and sensitive categories (health, finance, kids) often take longer. Policy issues surface as warnings in Play Console; unresolved warnings block the release.
What is the difference between Play App Signing and my upload key?
The upload key signs the AAB you upload; Play App Signing uses a separate app signing key, managed by Google, to sign what users install. You keep the upload key; Google keeps the signing key safe — you can request a reset of the upload key if you lose it.
Can I publish to specific countries only?
Yes. Country targeting in Play Console lets you choose where the app is available. This matters for legal compliance (GDPR in the EU, data laws by region) and for rolling out gradually — start with a small set of countries and expand.