How to Publish an App on Google Play in 2026: Complete Step-by-Step Guide

Publishing an app on the Google Play Store in 2026 takes more than simply uploading an APK. The Google Play Console has gone through significant changes over the past few years, including mandatory closed testing for new apps. This guide covers every stage — from creating your developer account to final approval.

1. Create a developer account on the Google Play Console

The first step is to access the Google Play Console and create a developer account. You will need:

• A Google account (Gmail)
• To pay the one-time US$25 fee
• To verify your identity (photo ID)
• To provide a valid address

Identity verification was introduced in 2023 and is mandatory. Google may take 2 to 7 business days to approve your account.

2. Prepare the app for publishing

2.1 Generate the App Bundle (.aab)

Google Play no longer accepts APKs as of August 2021. You need to generate an Android App Bundle (.aab). In Flutter, use flutter build appbundle --release. In React Native, the process is handled through Gradle.

2.2 Set up app signing

Google Play App Signing is mandatory. Google manages the distribution signing key, while you keep the upload key. Configure this the first time you upload the app.

2.3 Complete the store listing

The Store Listing requires:

• Title — up to 30 characters
• Short description — up to 80 characters
• Full description — up to 4,000 characters
• Icon — 512×512px, 32-bit PNG
• Screenshots — minimum 2 (phone), 8 recommended
• Feature graphic — 1024×500px
• Content rating — mandatory questionnaire

3. Mandatory closed testing

This is the stage that stops most developers. Since November 2023, Google requires every new app to go through a closed testing program before it can be published to production.

Closed testing requirements

• Minimum of 12 testers — with an active opt-in through Google Play
• 14 consecutive days — of real testing in the app
• Physical devices — emulators are detected and rejected
• Real Google accounts — fake or freshly created accounts are discarded
• Organic usage — Google analyzes session time, flows and interactions

This is where most independent developers get stuck. Getting 12 people committed to testing for 14 days is hard. Telegram groups with fake testers don't work — Google detects and discards them.

4. Production access form

After completing the 14 days of closed testing, you need to fill out the production access request form. In it, Google asks:

• What was tested during the testing cycle
• How many testers actively participated
• Which bugs were found and how they were fixed
• Why the app is ready for all users
• Whether the app collects sensitive data and how it is protected

A poorly completed form is one of the main reasons for rejection. Be specific, cite numbers and show that the app was genuinely tested.

5. Google review and publishing

After submitting the production form, Google takes 3 to 7 business days to review it. If approved, your app is published automatically on the Play Store.

If rejected, you'll receive an email with the reason. The most common ones:

• Metadata violation — misleading title, icon or description
• Policy violation — the app doesn't comply with Google's policies
• Insufficient testing — too few testers or an incomplete cycle
• Limited functionality — the app doesn't provide enough value

6. A realistic timeline: from zero to the Play Store

Estimated total: 3 to 4 weeks from zero to publishing, assuming the app is already finished and closed testing runs without issues.

7. The most common mistakes when publishing on Google Play

1. Using testers from Telegram groups — fake accounts, no commitment, Google detects and discards them.
2. Hiring bot services — emulators and automations are detected by the Play Integrity API.
3. A generic production form — vague answers like "I tested it and it worked" lead to rejection.
4. Low-quality screenshots — blurry images or incorrect frames make a bad impression.
5. Missing privacy policy — mandatory for any app that collects data.
6. Outdated target API — Google requires the targetSdkVersion to meet current requirements (API 34+ in 2026).

Frequently asked questions

← Back to the blog