Stage 1: account status — can you actually publish?

  • Log in on your own device and confirm you are owner, not just admin
  • Developer profile and identity verification are in good standing
  • Payments profile works; payout details set if you sell or use in-app purchases
  • Check account type and create date: new personal accounts need closed testing, organizations do not
  • No policy warnings or suspension notices in Console

Do this first on any purchased account. Pause on any field that disagrees with the written sheet before uploading anything. See the first-week-after-handover guide.

Stage 2: build and signing

  • Package name is final and avoids example domains and others' brands
  • targetSdk meets the current floor and is regression-tested
  • Ship an AAB, with 64-bit libraries if you use native code
  • Play App Signing enabled; upload keystore backed up twice
  • versionCode increments and versionName is right
  • One successful upload to internal testing with no hard warnings

The target API, package name and Play App Signing guides explain these in detail.

bash
# Build the release AAB
./gradlew clean bundleRelease

# Check the output and its upload-key signature
ls app/build/outputs/bundle/release/
jarsigner -verify -verbose -certs app/build/outputs/bundle/release/app-release.aab | tail -n 5

Also useful in this topic cluster:

Stage 3: store listing

ItemKey requirementCommon issue
App nameNo prices, rankings or misleading wordsOverlong or keyword-stuffed
Short / full descriptionAccurate, no exaggerationUnsupported 'No.1' or 'official'
Icon512×512, nothing misleadingToo close to another brand
ScreenshotsReal UI, at least twoUnrelated promotional images
Developer contactWorking email and siteTypo in email so notices are lost
Privacy policyPublic HTTPS link404 or login wall

Store assets are both conversion tools and policy review targets. Calm wording that matches the app minimises flags.

Stage 4: compliance declarations

  1. Data safety form consistent with policy and SDK behaviour
  2. Content rating questionnaire answered honestly
  3. Target audience set without accidentally triggering Families policy
  4. Ads declaration and app access with reviewer credentials
  5. Special declarations for finance, health, news and government
  6. Permission declarations explaining sensitive permissions

Dedicated guides cover the data safety form and app content/ratings. Everything must show complete before submission.

Stage 5: testing

  • Internal testing verifies install, login and core flow
  • New personal accounts: closed test of 12 testers for 14 days and a production request
  • Read the pre-launch report and fix crashes and accessibility findings
  • Try on at least two OS versions and two screen sizes on real devices
  • Confirm the app survives offline and weak networks

Write feedback down; it feeds the production access questionnaire and later retrospectives.

Stage 6: submit and watch week one

When creating the production release, choose countries, add release notes per language, confirm the policy status page is clear and submit. The first review can take days; avoid repeatedly withdrawing and resubmitting, which re-queues you.

During week one, check crash rate, ANRs, ratings and policy notices daily. Pause a staged rollout if metrics look wrong. Update handover docs with keys, permissions and procedures so staff changes do not lose critical info.

Not started yet? Do these three things

  1. Confirm the account type fits your app category (restricted categories usually need an organization)
  2. Fix the package name, signing approach and privacy policy
  3. Draw a schedule: internal → closed → submit, with buffer at each step

If you plan to buy an account first, put these in your inquiry spec and talk on Telegram @hagee66; any price is quoted there by spec, never on the site.

Related reading:

Related

Related desks