Publishing an Android app is less about the upload and more about the paperwork around it. The build takes minutes. The store listing, policy declarations and testing requirement are what stretch a launch into weeks. Here is the whole path, in the order you actually hit it.
Step 1: Create a developer account
Go to the Google Play Console and pay the one-time registration fee (US$25 at the time of writing). You choose between a personal and an organisation account at sign-up, and the choice matters more than it looks:
- Personal accounts created after 13 November 2023 must complete a closed test before they can apply for production access.
- Organisation accounts need a D-U-N-S number and verified business details, but skip that requirement.
You cannot convert one to the other later without support involvement, so pick deliberately. Identity verification can take a few days; start it before your app is ready, not after.
Step 2: Prepare the build
Google Play only accepts Android App Bundles (.aab) for new apps. In Android Studio: Build → Generate Signed Bundle / APK → Android App Bundle.
Three things to get right before your first upload, because changing them later is painful:
- applicationId — permanent. You cannot change it after publishing, ever.
com.mycompany.myapp, notcom.example.myapp. - versionCode — an integer that must increase with every single upload, including ones you later discard.
- Your keystore — back it up somewhere you will still have in five years. Losing it used to mean losing the app.
Step 3: Create the app in Play Console
All apps → Create app. You will set the default language, the app name (30 characters), whether it is an app or a game, and free or paid. Free cannot be switched to paid later — only paid to free.
Step 4: The assets Play will not let you skip
Play Console blocks publishing until all of these exist:
- App icon — 512 × 512 px, 32-bit PNG, under 1 MB, no transparency.
- Feature graphic — 1024 × 500 px, no alpha. Mandatory for every app.
- Phone screenshots — at least 2, up to 8.
- Short description — 80 characters. This is the line that sells the install.
- Full description — up to 4000 characters.
- Privacy policy URL — public, non-editable, and it must mention your app by name.
You can generate the icon set, the feature graphic and the policy here in a few minutes each: icon generator, feature graphic maker, privacy policy generator.
Step 5: App content declarations
This section is where first-time publishers lose the most time. You must complete every one of:
- Privacy policy URL
- Ads — whether your app contains them
- App access — if any part is behind a login, you must supply working test credentials
- Content rating questionnaire
- Target audience and content
- Data safety
- Government apps, financial features, health declarations where relevant
The Data safety form is the one that gets apps rejected, because it is cross-checked against your privacy policy. If the policy says you collect nothing and the form declares device identifiers, that mismatch is a policy violation on its own.
Step 6: Closed testing (personal accounts)
If you have a personal account created after 13 November 2023, this is mandatory before production. You need testers opted in continuously for a fixed window — currently 12 testers for 14 days — and then you apply for production access with written answers about how you recruited them and what feedback you got.
The clock starts when your twelfth tester has opted in, not when you sent invitations. Track it with the closed testing tracker so you are not counting from the wrong day.
Step 7: Production release
Create a production release, upload the AAB, write release notes, pick your countries, and submit. Review typically takes a few days for a new app and can be longer for a first submission from a new account.
The realistic timeline
- Day 0: developer account created, identity verification submitted.
- Days 1–3: account verified; build, assets and listing prepared.
- Day 3: closed testing track live, invitations sent.
- Days 3–6: chasing opt-ins until the tester count holds.
- Days 6–20: the qualifying window. Ship at least one update; collect written feedback.
- Day 20: apply for production access.
- Days 20–27: production access review, then release review.
Three to four weeks is normal for a first app on a personal account. Plan launches around that, not around the two hours it takes to upload a bundle.
Google adjusts registration fees, tester counts and testing durations periodically. Confirm current numbers against the Play Console Help pages before committing to a launch date.