How to Publish an Android App on Google Play (2026 Complete Guide)

Publishing on Google Play is more involved than it used to be. Since 2023, personal developer accounts must complete a closed testing period before going live — and that alone adds 2-4 weeks to the process. This guide walks through every step, in order, with the current requirements.

Overview: the full process

1. Create and verify a Google Play developer account ($25)
2. Prepare your app build (APK or AAB)
3. Set up your store listing
4. Complete closed testing (12 testers, 14 days)
5. Request production access
6. Go live

Each step has its own requirements. Skipping ahead or doing them out of order wastes time — Play Console won't let you proceed without completing prerequisites.

Step 1: Create a developer account

Go to play.google.com/console and sign in with a Google account. You'll be prompted to register as a developer — choose between a personal account (your name is shown publicly) or an organization account (your business name is shown).

Pay the one-time $25 registration fee by credit or debit card.

Complete identity verification: upload a government-issued photo ID and a selfie. This is required for all new accounts since 2023. Verification typically takes a few hours to 1 business day.

Once verified, your account is active and you can start creating apps.

Step 2: Create your app in Play Console

1. In Play Console, click Create app
2. Enter your app name, default language, whether it's an app or game, and whether it's free or paid
3. Accept the developer policies
4. Click Create app

This creates a shell in Play Console. You haven't uploaded anything yet.

Step 3: Prepare your app build

Google Play requires an Android App Bundle (AAB) format for new apps. APKs are still accepted for some cases but AAB is preferred and required for most new submissions.

In Android Studio, go to Build → Generate Signed Bundle / APK, select Android App Bundle, and sign it with your keystore. Keep your keystore file and password safe — losing it means you cannot update your app in the future.

Before uploading, test the build on a real device or emulator to confirm it installs and runs without crashes.

Step 4: Set up your store listing

Go to Store presence → Store listing in Play Console. Fill in:

• App name — up to 30 characters, shown on the Play Store
• Short description — up to 80 characters, appears below the title
• Full description — up to 4,000 characters, shown on the app's page
• Screenshots — at least 2 phone screenshots required. Tablet screenshots optional but recommended.
• Feature graphic — 1024x500px banner, required for most app categories
• App icon — 512x512px PNG with no alpha channel
• Category — pick the most accurate one
• Contact details — email address is required
• Privacy policy URL — required if your app collects any user data

You can save a draft and come back. The listing doesn't need to be complete to start testing — but it must be complete before you apply for production access.

Step 5: Complete required policy sections

In the left sidebar under Policy, complete:

• App content — content rating questionnaire (mandatory), ads declaration, target audience
• Data safety — declare what data your app collects and how it's used

These must be completed before you can publish to any track. The content rating in particular trips up many first-time developers — it's a multi-step questionnaire in the App content section, not automatic.

Step 6: Upload your build to internal testing

Before closed testing, do a quick internal test to verify your build is valid:

1. Go to Testing → Internal testing
2. Click Create new release
3. Upload your AAB file
4. Add release notes (can be brief)
5. Click Save and publish

Internal testing releases go live within minutes. Add your own Gmail address as a tester and install the app from the Play Store link to confirm everything works end-to-end.

Step 7: Set up closed testing

This is the longest step for personal accounts. You need 12 active testers for 14 consecutive days.

Create a Google Group: Go to groups.google.com and create a new group. This will be your tester list.

Create a closed testing track: Go to Testing → Closed testing → Create track. Add your Google Group as the tester list.

Publish to the closed track: Upload your AAB (same as step 6 or a newer version) and publish it to the closed track.

Get testers: Share the Google Group invite and the opt-in link (from Play Console) with at least 12 people. They must open the opt-in link on an Android device and install the app. Simply joining the Google Group is not enough.

Getting 12 testers is often the slowest part of the entire process. Methods that work:

• Mutual testing exchanges like AppSwap — fastest and free, testers have an incentive to complete all steps
• Developer Telegram and Discord communities
• Personal contacts who own Android phones

Once 12 testers are active, the 14-day counter starts automatically in Publishing overview. You can track progress there.

Step 8: Request production access

After 14 days with 12+ active testers, a "Request production access" button appears in Publishing overview. Click it and fill out the form describing your app, target audience, and monetization model.

Before submitting, verify your store listing is fully complete — screenshots, feature graphic, privacy policy, content rating. Incomplete listings are a common reason for rejection.

Google reviews the request manually. For new accounts this typically takes 3-7 business days. You'll receive an email when the review is done.

Step 9: Publish to production

Once production access is granted, go to Production → Create new release, upload your AAB, and publish. You can choose a staged rollout (starting at 10-20% of users) or full rollout.

For a first launch with no existing users, full rollout is fine. The app will be live on the Play Store within a few hours.

Total time to expect

• Account setup and verification: 1-2 days
• Store listing and policy sections: 1-2 days
• Finding 12 testers: 1-7 days (faster with a mutual exchange)
• Closed testing period: 14 days minimum
• Production access review: 3-7 business days

Minimum realistic timeline from starting your account to going live: 3-4 weeks. Plan accordingly.

Frequently asked questions

Related articles