How to Publish an Android App on Google Play in 2026: Step by Step
Publishing an Android app on Google Play takes eight steps: create and verify a developer account, build a signed AAB, create the app, write the listing, complete the declarations, run closed testing, submit for review, then release. Here is each one with the 2026 rules.
Direct answer: publishing an Android app on Google Play takes eight steps — create and verify a developer account, build a signed AAB, create the app in Play Console, write the store listing, complete every content declaration, run closed testing, submit the production release for review, then publish. The one-time cost is 25 USD. The realistic timeline is two to seven days for an organisation account and three to five weeks for a personal account, because of the 12-tester rule.
Almost every rejected first submission fails on steps 5 and 6, not on the app itself. Work through them in order.
The eight steps at a glance
| Step | What it is | Typical time |
|---|---|---|
| 1 | Developer account + identity verification | 1–3 days |
| 2 | Signed release AAB | Under an hour |
| 3 | Create the app in Play Console | 5 minutes |
| 4 | Store listing (text + graphics) | 1–3 hours |
| 5 | Content declarations | 1–2 hours |
| 6 | Closed testing, 12 testers, 14 days | 14 days (personal accounts) |
| 7 | Production release + review | Hours to 7 days |
| 8 | Rollout, updates, monetization | Ongoing |
Step 1: Create and verify a Google Play developer account
Register at the Play Console with a Google account, pay the one-time 25 USD fee, and complete identity verification. A personal account needs a government photo ID and a physical address that matches it. An organisation account needs a D-U-N-S number for the legal entity, which is free but can take up to 30 days to issue if you do not already have one.
Verification typically clears in one to three days. The usual failure is an address on the form that does not match the address on the ID document — fix that before you resubmit, not after.
Step 2: Build a signed release AAB
Google Play requires the Android App Bundle (.aab) for all new apps. In Android Studio: Build → Generate Signed Bundle / APK → Android App Bundle, then sign with a release keystore. Two rules worth writing down:
- Enrol in Play App Signing. Google holds the final signing key. If your local keystore is ever lost, you can still ship updates. Without it, a lost keystore permanently ends your ability to update that app.
- Back the keystore and its passwords up off the build machine. Not in the repository.
Before anything goes live under your name, it is worth checking what is actually inside the bundle — permissions, SDKs, and network endpoints.
Step 3: Create the app in Play Console
In All apps → Create app, set the app name, default language, app-or-game, and free-or-paid. Free cannot be switched to paid later. That is the one decision on this screen that is irreversible, so make it deliberately.
Step 4: Complete the store listing
The limits, which have not changed for 2026:
| Asset | Requirement |
|---|---|
| App name | 30 characters |
| Short description | 80 characters — carries most store-search weight |
| Full description | 4,000 characters |
| Icon | 512 × 512 PNG, 32-bit, under 1 MB |
| Feature graphic | 1024 × 500 PNG or JPEG |
| Phone screenshots | Minimum 2, up to 8; 320–3840 px on the shorter side |
| Tablet screenshots | Required to be surfaced on tablets |
Put the primary keyword in the short description. Play's search index weights the title and short description far more heavily than the body text, and keyword-stuffing the full description reads as spam to both Google and to the person deciding whether to install.
Step 5: Fill in every content declaration
This is where first submissions die. The full set:
- Data safety — what the app collects, whether it is shared, whether it is encrypted in transit. Google tests the app against your answers, so an ad SDK that collects an advertising ID must be declared.
- Content rating questionnaire — generates the IARC ratings. Answer honestly; a mismatch is a removal, not a warning.
- Target audience and content — answering "children" pulls in the Families policy and its extra requirements. Do not select it casually.
- Ads declaration — declare in-app advertising if any ad SDK is present.
- Privacy policy URL — must be live, publicly reachable, and about this app. A 404 here is an instant rejection.
- News and government app declarations, plus the financial-features section if it applies.
Step 6: Run closed testing with 12 testers for 14 days
If your personal developer account was created after November 2023, Google requires a closed test with at least 12 testers opted in for 14 continuous days before it will grant production access. Create a closed track, add testers by email list or Google Group, and share the opt-in link. If the opted-in count drops below 12 during the window, the clock restarts. Organisation accounts are exempt from this requirement.
This single rule is why a solo developer's realistic timeline is weeks, not days, and it is the most common surprise for anyone publishing their first app in 2026.
Step 7: Create the production release and submit for review
On the Production track, choose Create new release, upload the AAB, write release notes, select countries, and send for review. Review runs from a few hours to seven days; a first release from a brand-new account sits at the slower end. Do not push edits while a review is in progress — changes can restart the clock.
Step 8: Publish, then plan updates and monetization
After approval the release rolls out and the listing becomes searchable within a few hours. Two habits that matter more than launch day:
- Staged rollout. Ship updates at 20 percent first. If the crash rate moves, halt the rollout before it reaches everyone.
- Get the ad implementation right before launch. If the app carries in-app advertising, interstitials that fire on app open, ads that cover navigation, and ads served to under-13 users without the right declarations are all removable offences. Ad density is a policy surface, not a growth lever.
Monetization is where most published apps stall: the app ships, installs trickle, and the ad revenue never becomes real because nobody is running acquisition, release cadence and mediation. If that is the part you do not want to own, how ad revenue sharing works explains the arrangement where an operator does the building, publishing and monetizing and the account holder keeps the publisher-of-record role.
Become a ConsoleMint publishing partner
If your Google Play developer account is in good standing, ConsoleMint can distribute the apps it builds, publishes and maintains through it, and share the in-app ad revenue with you. You get a fixed monthly payout while the apps are new and still ramping up, then a share of the ad revenue as installs accumulate — paid on the 1st–5th by UPI or bank transfer.
Talk to ConsoleMint → Developer-role access only. You keep the account and can revoke access with 30 days notice.The one-line summary
Eight steps, 25 USD once, and a timeline set by your account type: about a week for an organisation account, three to five weeks for a personal one because of the 12-tester closed-testing rule. Budget your care for the declarations in step 5, not the upload in step 7.
Frequently asked questions
How much does it cost to publish an app on Google Play?
25 USD, once, for life. That is the Google Play developer registration fee and it covers unlimited apps on that account. There is no annual renewal, unlike Apple. Beyond that, publishing itself is free; Google takes a service fee only on in-app purchases and subscriptions, and nothing at all on in-app advertising revenue.
How long does it take to publish an app on Google Play?
For an organisation account, roughly two to seven days: identity verification, then a review that runs a few hours to a week. For a personal account opened after November 2023, budget three to five weeks, because you must first run a closed test with at least 12 testers opted in for 14 continuous days before production access unlocks.
Do I need an APK or an AAB to publish?
An AAB, the Android App Bundle. Since August 2021 Google Play has required AAB format for all new apps. A bare APK is rejected at upload. Play generates the per-device APKs from your bundle, which is also why enrolling in Play App Signing matters: Google holds the final signing key and can re-sign the generated APKs.
Why do most first submissions get rejected?
Overwhelmingly on the declarations, not the code. The commonest causes are a Data safety form that contradicts what the app actually collects, a missing or unreachable privacy policy URL, a content rating that does not match the app, and a target-audience answer that puts the app in the children category without the extra requirements that triggers. Fix the declaration, resubmit, and the second review is usually faster.
Can I publish an app if I do not own a developer account?
Yes, through a partner whose account distributes it. That partner remains the publisher of record on the listing and grants the developer working on the app Developer-role access only, scoped to named apps and revocable from the Users and permissions screen. What is never acceptable is handing over the Google account password or its recovery codes: that breaches the Developer Distribution Agreement and puts the account at permanent risk.