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

Why the Play Store Matters More Than Ever

There are over 3 billion active Android devices in the world. The Google Play Store is the primary distribution channel for Android apps, the most trusted source of downloads for the majority of users, and the infrastructure that handles payments, reviews, and automatic updates at global scale. Publishing your app on Google Play transforms it from a file you share manually into a product your customers can discover, download in one tap, and trust implicitly. Whether you built your app using a no-code app builder or a custom development team, this guide walks you through every step to successfully publish your app on Google Play Store in 2026.

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

Go to play.google.com/console and sign in with your Google account. Click "Create developer account" and fill in your developer name (this is what users see on the Play Store — use your business name), email address, and website. Pay the one-time $25 registration fee via credit card. Google will verify your identity — this process may take 24–48 hours and may require a government-issued ID. If you are creating a personal account (as opposed to an organisation account), you will also need to verify you have access to a physical Android device using the Play Console mobile app before you can publish. Once verified, your Google Play Console account is active and ready.

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.

• It was originally 20 testers. Google reduced the requirement to 12 in December 2024 after developers reported it was unrealistic for solo publishers. If you read a guide (including older versions of this one) that says 20, it is out of date.
• 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. Ask friends, colleagues, or a beta community to join your closed test track and opt in early — the 14-day clock is the longest fixed delay in this entire process, so starting it late is the single most common reason a "quick" first launch stretches into a month.

Step 2: Get Your AAB File from Free App Maker Pro

Google Play has required AAB (Android App Bundle) format for all new app submissions since August 2021. APK is still accepted in two narrow cases — apps that existed before that date doing a signing-key upgrade, and private apps distributed through Managed Play — but for a new app in 2026, AAB is the only route onto the Play Store. This only affects Play Store submission: you can still build and distribute an APK directly, or to any other app store, at the same time — see our full APK vs AAB comparison if you want the complete picture. In our builder, select "AAB" as your export format before clicking Build. The AAB vs APK difference matters here: an AAB is a publishing format that lets Google's servers generate optimised APKs for each device configuration, reducing download size by up to 40% compared to a universal APK. Our Free App Maker Pro uses R8 minification to produce optimised AAB files — see our v2.4 update notes for technical details on AAB optimisation.

Target API Level: What You Must Ship By

Every year, Google raises the minimum Android API level your app must target to stay listed. Missing this deadline does not get your app rejected outright, but it does get it hidden from new users on newer devices — which quietly kills your growth without any error message to explain why.

• New apps and updates must target Android 16 (API level 36) or higher from 31 August 2026.
• Existing published apps must target at least Android 15 (API level 35) to remain visible to new users on devices running newer Android versions. Apps targeting API 34 or below still work for existing users, but stop reaching new ones on the latest phones.
• Google allows a one-time extension request to 1 November 2026, submitted through a form in Play Console, if you need more time.

If your app was built with Free App Maker, this is handled for you automatically — every build targets a current API level. If you are working with a developer or another builder, ask them directly which API level the app targets before you submit; this single question avoids the most invisible failure mode in this entire guide.

Personal or Organisation Account: Which Should You Choose?

Google Play Console offers two account types, and the choice affects everything covered above. 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 — faster to set up, no D-U-N-S number needed, but subject to the 12-tester/14-day closed testing requirement described above if created after 13 November 2023. Best for a solo founder or a first app where you want to publish quickly and can round up a dozen testers.
• Organisation account — requires a D-U-N-S number (a free business identifier you can request from Dun & Bradstreet, though issuance can take 5–30 days if you do not already have one), and Google verifies your business registration. In exchange, you skip the closed testing requirement entirely and your listing shows as published by a verified business, which reads as more credible to users.

If you already have a registered business and are not in a rush, request the D-U-N-S number first — the wait for it can run longer than the 14-day testing period you would otherwise need to complete. If you need to publish this week, start with a personal account and begin closed testing immediately.

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 (you cannot change from paid to free later)

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

This is the most important step for discoverability. 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. Include your keyword phrases 3–5 times naturally.
• Screenshots: Upload at least 2 phone screenshots. High-quality screenshots with device frames and context text perform significantly better in search.
• 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. This must match the icon inside your app file.

Step 6: Complete Content Rating and Data Safety

Two mandatory sections often trip up first-time publishers.

Content Rating (IARC): Navigate to "Policy > App content > Content rating". Complete the IARC questionnaire by answering questions about your app's content — violence, sexual content, language, etc. For a typical business or informational app, all answers will be "No" and you will receive an "Everyone" rating. This is required before you can publish.

Data Safety Form: Navigate to "Policy > App content > Data safety". Declare what data your app collects and shares. For a basic WebView app, if your website uses cookies or Google Analytics, you must declare collection of "Browsing history" and "Analytics data". If you use push notifications, declare collection of notification token data. The form is mandatory for every app, even one that collects no data at all — you still fill it in and confirm that. Google has rejected non-compliant submissions on this basis since 20 July 2022, and continues to. Be honest — Google cross-checks declared data against your app's behaviour. Inaccurate declarations are a common reason for Play Store review rejections.

Step 7: Submit for Review

Once all checklist items show green ticks, navigate to Release > Production and click "Send X changes for review". Google's own guidance is to budget up to 7 days for review, though most apps clear faster than that. Do not edit your store listing while a review is in progress — Google states this can restart the review clock, so finish your listing completely before you submit rather than tweaking it afterwards. You will receive an email notification when your app is approved or if action is required. While waiting, you can set up pre-registration or prepare your launch marketing.

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: Missing privacy policy URL, too-short description, or missing screenshots. Fix: complete every field and add a valid privacy policy page to your website.
• 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.
• Low-value app (spam policy): Apps that simply mirror a website with no added functionality. Fix: add at least one app-specific feature — push notifications, an offline page, or a home screen shortcut to a specific function.
• 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

The summary below covers the essentials; for keyword research, the exact line between optimising and Google's keyword-stuffing policy, and what to track after launch, see our full ASO guide. App Store Optimisation is the practice of improving your app's visibility in Play Store search results. It works on the same principle as SEO for websites — see our guide on WebView vs native apps if you have not decided on your app's architecture yet — but the levers are specific to Play Store. These are proven to move both ranking and conversion:

• Put your most important keyword in the app title (it carries roughly 3x the weight of description keywords)
• Use the full 4,000 characters of your description — longer, keyword-rich descriptions rank higher
• Upload the maximum number of screenshots (8) with captions explaining each feature, not just bare UI shots — a caption stating the benefit converts better than the screenshot alone
• Actively collect ratings within the first 30 days — apps with ratings above 4.0 rank significantly higher, and the first 30 days carry disproportionate weight in how the algorithm initially places your listing
• Update your app regularly — Google rewards active developers with higher visibility, and a stale "last updated" date is a small but real trust signal users check before downloading
• Localise your listing for your target markets — a Spanish listing for Spanish-speaking users dramatically increases conversion rates, and you do not need to translate the app itself first to localise the listing text
• Choose your app's category carefully in Play Console — the wrong category buries you against irrelevant competitors, while the right one puts you in front of users actively browsing for what you offer

After You Publish: What to Monitor

Getting approved is the start, not the finish. Once your app is live, three things determine whether it keeps growing.

• Ratings and reviews. Reply to reviews, especially critical ones — a developer response signals an active, maintained app to anyone reading before they download. Apps with a rating above 4.0 are shown more often in search and category browsing.
• Crash reports and ANRs (App Not Responding). Play Console's dashboard flags these automatically. A rising crash rate after an update is the single fastest way to lose your ranking, since Google's own ranking signals factor in stability.
• Staged rollouts for updates. Rather than pushing an update to 100% of users immediately, release it to a small percentage first (Play Console lets you choose the rollout percentage). If something is wrong, you catch it before it reaches everyone.

If your app is a WebView wrapper, remember that most of what your users see lives on your website, not inside the app package — so keeping your site fast and error-free is just as much a part of "app maintenance" as anything inside Play Console. Run your site back through our WebView Compatibility Checker periodically, especially after any redesign, to catch anything that would newly break inside the app shell.

Frequently Asked Questions

Do I need a Google Play developer account to test my app?
No. You can install and test an APK directly on any Android device without a developer account. The $25 account is only required when you are ready to publish to the Play Store. See our step-by-step conversion guide for how to sideload your APK for testing.

What is the difference between AAB and APK for Play Store submission?
An APK (Android Package) is a complete, ready-to-install file. An AAB (Android App Bundle) is a publishing format that lets Google generate device-specific APKs, which are smaller and more efficient. Google Play requires AAB for new apps. Our builder generates both formats — use AAB for Play Store submission.

Do I need 12 testers before I can publish?
Only if you registered a personal Google Play developer account after 13 November 2023. You need 12 testers opted in for 14 continuous days before you can request production access. Organisation accounts are exempt. This was 20 testers before Google reduced it in December 2024.

Can I still submit an APK instead of an AAB?
Not for a new app. Google Play has required AAB for new submissions since August 2021. APK is only still accepted for pre-2021 apps doing a signing-key upgrade, or for private apps on Managed Play. Building an APK for distribution outside Google Play is unaffected.

How long does Google Play review take?
Google's own guidance is to budget up to 7 days, though most apps clear faster. Avoid editing your store listing while a review is in progress, since Google states that can restart the clock. Updates to an already-approved app are usually reviewed faster than a first submission.

Can I publish a WebView app on Google Play?
Yes, with the caveat that your app must provide genuine utility beyond simply mirroring a website. Adding push notifications, offline capability, or a custom navigation experience satisfies Google's policy requirements.

What happens if my app gets rejected?
You will receive an email with specific reasons for rejection. Fix the identified issues, update your app or listing as needed, and resubmit. There is no penalty for a first-time rejection, and most issues are straightforward to resolve.

Conclusion

Publishing on Google Play Store is the most powerful distribution move you can make for your Android app. With 3 billion potential users, automatic update delivery, and the trust signal of a verified Play Store listing, the $25 investment pays for itself with your first handful of new customers. Build your AAB with our tool, follow this guide step by step, and your app can be live on Google Play within a week. For tips on maximising your app's impact after launch, read our guide on 5 reasons your website needs a mobile app.