How to Publish Your Android App on Google Play Store in 2026

Why the Play Store Matters More Than Ever

Google Play gives Android users a storefront to discover, install, review and update your app. For a website-based app, the submission starts with a signed Android App Bundle and a working site the review team can access. This guide covers the account, test track, listing and review steps so you can plan them before paying for publishing files.

Prerequisites Checklist

Before you begin the submission process, gather and prepare the following:

• Your AAB file (Android App Bundle — the format Google Play requires, not APK)
• A Google account dedicated to your developer identity
• A credit or debit card for the one-time $25 registration fee
• A published privacy policy URL (required for all apps)
• If this is a new personal account: 12 people willing to test your app for 14 continuous days — see the closed testing section below before you start, since this is usually the longest delay in the whole process
• App screenshots: at least 2, up to 8, for phone (1080x1920px recommended)
• A feature graphic: 1024x500px banner image for your Play Store listing
• A high-resolution app icon: 512x512px PNG with transparent background
• A short description (80 characters max) and full description (4,000 characters max)

Step 1: Create Your Google Play Developer Account

Sign in at Play Console, choose the account type that matches the publisher and pay the one-time $25 registration fee. Google asks for identity and contact information. New personal accounts may also have to verify access to an Android device using the Play Console mobile app. Follow the official registration checklist for your account.

The Closed Testing Requirement for New Personal Accounts

This is the step that catches the most first-time publishers off guard in 2026, and a lot of older guides still get the numbers wrong. If your Google Play developer account is a personal account created after 13 November 2023, Google requires you to run a closed test with at least 12 testers, opted in continuously for 14 days, before you can apply for production access. See Google’s closed-testing requirements. Keep a record of how testers used the app and which problems you fixed. The production access application asks about the test.

• The 14 days must be consecutive. A tester who opts in, drops out after a week, then opts back in does not count — Google's own guidance is explicit that the 14 days will not add up across a gap.
• Organisation accounts are exempt. This requirement applies only to personal accounts. If you register as a business (which also requires a D-U-N-S number), you skip this step entirely.
• Recruit testers before you build your listing. Invite testers before launch planning. Ask them to complete your key task on their own phones and tell you where they get stuck.

Step 2: Get Your AAB File

Use an Android App Bundle (AAB) for a new Play app. Google Play generates installable APKs from the bundle. Eligible apps created before August 2021 can still use APKs under Google’s release rules. Read the APK vs AAB comparison if you are choosing between direct Android installation and Play distribution.

Free App Maker offers a free build preview with a one-time APK download unlock. The Play Store Pack is a separate purchase for an eligible app. It includes an AAB, key material and supporting files. Review the supplied policy and listing drafts for your site before uploading from your own Play Console.

Target API Level: What You Must Ship By

Check Google Play’s current target API requirements for your device category before creating the release. The target API of your AAB controls whether you can submit a new app or update. Older targets can also limit discovery of an existing app on newer devices. Compare the target shown in your uploaded bundle’s details with the current rule before planning your launch date.

Personal or Organisation Account: Which Should You Choose?

Google Play Console offers two account types, and the choice affects everything covered above — most importantly, whether the 12-tester rule applies to you at all. We set out both routes plainly on the page for the files you need to publish your app on Google Play. See our dedicated guide on developer account cost and requirements for the full breakdown, including the D-U-N-S number process for organisation accounts.

• Personal account — for individual publishers. The 12-tester, 14-day closed-testing requirement applies to personal accounts created after 13 November 2023.
• Organisation account — generally requires a D-U-N-S number and business verification. See Google’s account documentation for requirements and exceptions.

Choose based on the actual publisher. Check whether your business already has a D-U-N-S number before applying for another. For a new personal account, budget time for the closed test and the production access review.

Step 3: Create Your App in Play Console

In Google Play Console, click "Create app". Fill in:

• App name: Your app's display name (up to 30 characters)
• Default language: Your primary language
• App or Game: Select "App"
• Free or Paid: Choose whether your app is free or paid (once offered for free, the same app cannot be changed to paid)

Agree to the developer program policies and click "Create app". You will land on your app's dashboard, which shows a setup checklist. Work through this checklist in order.

Step 4: Upload Your AAB and Set Release Notes

Navigate to Release > Production > Create new release. Click "Upload" and select your AAB file. Google will analyse the file and display version information. In the "Release notes" field, add a brief description of what is new in this version — even for your first release, write something like "Initial release." Click "Save" and then "Review release".

Step 5: Complete Your Store Listing

Navigate to "Store presence > Main store listing". Fill in every field:

• App name (30 chars): Include your primary keyword naturally — e.g., "MyBrand — Order Food Online"
• Short description (80 chars): Your most compelling one-sentence pitch. Include your top keyword.
• Full description (4,000 chars): Write naturally for users, not keyword stuffing. Explain what your app does, who it is for, and what makes it special. Use the terms that describe its actual features.
• Screenshots: Upload at least 2 phone screenshots. Start with the screen that best shows the main task.
• Feature graphic: This 1024x500 image appears at the top of your listing on many devices. It is your billboard — make it count.
• App icon: Upload your 512x512 icon. Use artwork that makes the app easy to recognise.

Step 6: Complete Content Rating and Data Safety

In App content, answer the content-rating questionnaire based on what people can actually access inside the app. For a WebView app, include the website screens and content it exposes.

Complete the Data safety form using the app’s actual collection and sharing. Check native SDKs and any website code you control that runs in the app. For example, go through login, a normal visit, analytics or advertising choices and account deletion. Match your answers and public privacy policy to what those flows do. Use prepared answers as a starting point and check them for your specific app.

Step 7: Submit for Review

Before sending changes from Publishing overview, test the release from a clean install. Open the app, complete the main action, check the Android back button and verify that reviewers can reach any restricted screens using the access instructions you provide. Review can take up to seven days and longer in some cases. Check Google’s publishing guidance and the current status in your Console.

Common Reasons Apps Get Rejected (and How to Fix Them)

The summary below covers the essentials; for the full policy-by-policy breakdown, including how to appeal a rejection you believe was a mistake, see our dedicated guide on why apps get rejected.

• Incomplete store listing: A missing privacy policy URL, required field or screenshot can block submission. Complete the fields flagged in your Console and test the public privacy link.
• Inaccurate data safety declaration: Your app collects data you did not declare. Fix: audit your website's tracking tools and declare all data types in the Data Safety form.
• Limited functionality or WebView spam: Review the exact policy in the notice. Test the real user task end to end and make sure you own the site or have permission to display it.
• Icon or screenshot violations: Screenshots showing competitor branding, misleading UI, or images that violate policies. Fix: use genuine screenshots of your own app only.
• Broken functionality: Google tests apps before approving them. If your website is down or loads an error page, the app will be rejected. Fix: ensure your website is stable and loads correctly before submitting.
• Skipping the closed testing requirement: New personal accounts that try to jump straight to production without completing the 12-tester, 14-day closed test get blocked at submission. Fix: start your closed test the moment your app is built, not after your listing is finished — see the testing section above.

App Store Optimisation (ASO) Tips

Use a title that clearly identifies the app, screenshots of the real workflow and a description that explains what users can do. Pick the category that matches the app’s purpose and make the listing language match the audience the app can serve. The app listing guide explains how to test a change and read its results.

After You Publish: What to Monitor

• Reviews: look for repeated reports about one task, device or release.
• Android vitals: check crashes and app-not-responding events after a release. Compare affected devices and app versions.
• Staged rollouts: release an update to a small share of users first when available. Keep the existing app working while you check the update.

After a site change, repeat login, navigation and checkout in the installed app. The WebView Compatibility Checker can help identify initial site issues. A real Android test checks the full journey.

Frequently Asked Questions

Do I need a Google Play developer account to test my app?
You can install a compatible APK directly on Android for testing without a Play developer account. See the Android walkthrough for the steps.

What is the difference between AAB and APK for Play Store submission?
An APK is an installable Android file. An AAB is the format for publishing a new Play app. Play turns it into APKs for supported devices. The Play Store Pack includes the AAB for an eligible app.

Do I need 12 testers before I can publish?
The 12-tester rule applies to personal developer accounts created after 13 November 2023. Keep at least 12 testers opted in continuously for 14 days, then apply for production access.

Can I still submit an APK instead of an AAB?
New Google Play apps require an AAB. Apps created before August 2021 may still be eligible to upload APKs under Google’s release rules.

How long does Google Play review take?
Allow up to seven days and longer in some cases. Google considers the most recently submitted changes when calculating review turnaround.

Can I publish a WebView app on Google Play?
A WebView app can be eligible if you have permission to display the website and the app meets Google Play’s functionality and other policies. Test the actual user journey before submitting.

What happens if my app gets rejected?
Read the policy notice and fix each issue it identifies. If you believe the finding is incorrect, use the appeal route in the notice.

Conclusion

Choose the correct Play Console account, test the Android app, then submit the AAB, listing and declarations together. If your test requires a login, verify that a reviewer can follow the access instructions without your help. Schedule the launch around the review status shown in your account.