How to Publish an Android App to the Google Play Store
By Appilix Software
July 28, 2026
Getting your app built is one thing. Getting it live on the Google Play Store is a whole different process — and if you are doing it for the first time, it can feel overwhelming. There are store listings to fill out, declarations to complete, content ratings to set up, testing tracks to configure, and a review process to pass. Miss one step and your submission gets rejected.
This guide walks you through the entire process from start to finish. No steps skipped, no assumed knowledge. By the end of it you will have your app live on the Play Store and available to anyone with an Android device.
One important thing before we dive in — Google Play no longer accepts APK files for new app submissions. The only accepted format is AAB (Android App Bundle). Make sure you have your signed AAB file ready before continuing.
Let's get started.
Before you log into the Play Console, make sure you have everything ready. Going in without these will slow you down mid-process.
A Google Play Developer Account
If you do not have one yet, go to play.google.com/console and sign up. There is a one-time registration fee of $25. You will need a Google account and a valid payment method to complete the registration. Once approved, your account stays active permanently.
A Signed AAB File
Google Play only accepts AAB format for new app submissions. Make sure your AAB is signed with a release keystore — a debug build will not be accepted. Keep your keystore file somewhere safe because you will need the same keystore for every future update to this app. Losing it means you cannot update the app ever again.
App Assets
You will need the following ready before filling out the store listing:
For screenshots, you do not need to submit raw screen captures. A much better approach is to present them inside a clean device mockup — it looks more professional and performs better on the store listing. If you need a quick way to do that, Appilix's Free App Store Screenshot Generator lets you upload your captured screenshots and wrap them inside beautiful device mockups for Android phone, Android tablet, iPhone, or iPad. No design skills needed.
A Privacy Policy URL
Google requires a privacy policy for all apps on the Play Store. It needs to be hosted on a publicly accessible URL — your website works fine for this. If you do not have one yet, there are free privacy policy generators online that can get you started.
App Description
Have your short description and full description written and ready. The short description has a limit of 80 characters. The full description allows up to 4000 characters. Having these prepared in advance saves time when filling out the store listing.
Go to play.google.com/console and log in with your developer account. From the dashboard, click Create app in the top right corner.
You will see a form with the following fields to fill in:
App name
This is how your app will appear on Google Play. You have a limit of 30 characters so keep it short, clear, and easy to search for.
Package name
This is the unique identifier for your app — for example com.yourname.myapp. You have up to 150 characters. Once your app is published, this cannot be changed, so make sure it is correct before moving forward. Use the Check availability button to confirm your package name is not already taken.
Default language
Select the primary language your app is in. English (United States) is selected by default.
App or game
Select whether your submission is an app or a game. You can change this later in Store settings if needed.
Free or paid
Choose whether your app will be free or paid. Once your app is published, you cannot change it from free to paid. You can however switch from paid to free at any time.
At the bottom of the form you will also find two declarations you need to confirm before creating the app:
Check both boxes and click Create app.
Once your app is created, go to Grow users → Store presence → Store Listings from the left sidebar. This is where you set up everything users will see when they find your app on the Play Store.
App name
Your app name can be up to 30 characters. Keep it clear and relevant to what your app does.
Short description
This appears right below your app name on the store listing. You have 80 characters to work with. Make it count — it is the first thing users read before deciding whether to scroll further.
Full description
You have up to 4000 characters here. Describe what your app does, who it is for, and what makes it useful. Write for the user, not just for search. Avoid keyword stuffing — Google's algorithms and reviewers both flag that.
App icon
Feature graphic
This is the banner image that appears at the top of your store listing.
Screenshots
Screenshots are what convince users to download your app. You need a minimum of 2 and can upload up to 8.
Rather than uploading plain screen captures, present your screenshots inside device mockups — it looks far more professional and makes a real difference on the store listing. You can use the Appilix's Free App Store Screenshot Generator to wrap your screenshots inside clean Android phone, Android tablet, iPhone, or iPad mockups quickly and for free.
Once everything is filled in, click Save before moving on.
Go to Grow users → Store presence → Store Settings. This page has two important things to complete — your app category and your store listing contact details.
App category
This is more important than most developers realize. The category you choose directly affects how and where your app appears in Play Store search results and browse pages. Picking the wrong category does not just hurt discoverability — it can also trigger a rejection during review if Google determines your app does not belong where you placed it.
First, select whether your app is an App or a Game. This cannot be changed after your app is published so make sure you get it right.
Next, select a Category. Some common app categories include:
Pick the category that most accurately describes what your app does — not the one that has the most competition or the one you think will get more downloads. Google's reviewers check this and users searching within a category expect to find apps that actually belong there.
Finally, add Tags. Tags help Google better understand what your app is about and surface it in relevant searches. You can add up to five tags. Choose tags that genuinely reflect your app's core features and audience.
Store listing contact details
Below the category section, fill in your contact details:
Click Save once everything is filled in.
Go to Monitor and improve → Policy and programs → App content from the left sidebar. You will see a list of declarations that need to be completed before your app can go live. Work through each one until they all show a green checkmark.
Health apps
Declare whether your app provides health-related features or medical advice. If it does not, simply select that it is not a health app.
Advertising ID
Declare whether your app uses the advertising ID to track users for ad targeting purposes. If your app does not show ads or use any ad SDK, select that it does not use the advertising ID.
Financial features
Declare whether your app involves any financial transactions, banking, cryptocurrency, or investment features. If it does not, select that it has no financial features.
Government apps
Declare whether your app is an official government app. Most apps simply select that they are not.
Data safety
Tell Google what data your app collects, how it is used, and whether it is shared with third parties. Be accurate here — Google cross-checks this against your privacy policy and your app's actual behavior.
Target audience and content
Declare who your app is intended for. If your app targets children under 13, additional restrictions apply under Google's Families Policy.
Content ratings
Fill out a questionnaire about your app's content. Google uses your answers to assign an age rating that appears on your store listing.
Sign in details
If your app requires a login to use, provide Google's review team with test credentials so they can access and review the app properly.
Ads
Declare whether your app contains ads. If it does, select the ad type. If it does not, select that it contains no ads.
Privacy policy
Paste the URL of your publicly accessible privacy policy. This is mandatory for all apps on the Play Store.
Foreground service permissions
If your app uses foreground services — such as running a process while the app is in the background — declare what type of service it is and why it is needed.
Before we get into the steps, there is something important to know. If your Google Play Developer account is registered as an organization, you already have direct access to publish to Production without going through any mandatory testing period. You can skip straight to the Production track and submit your app for review immediately.
If your account is a personal account, Google requires you to complete a mandatory closed testing period before you can apply for production access. We will cover that in detail below.
Google Play has four release tracks. Each one serves a different purpose:
If you are on a personal account, this is a mandatory step you cannot skip. Google requires at least 12 testers to actively test your app for a minimum of 14 consecutive days under the closed testing track before you can apply for production access.
Here is how to set it up:
A few important things to keep in mind:
Once the 14-day period is complete, you will see the option to Apply for production access in the Play Console. Google then reviews your application — this typically takes a few days.
Whether you are uploading to the closed testing track or directly to production, the process is the same. Go to your selected track, click Create new release, and upload your signed AAB file.
Make sure you are uploading a release-signed AAB and not a debug build. Google will reject unsigned or debug builds immediately.
Release notes appear on the Play Store under What's new. For your first release you can keep it simple — something like "Initial release" works fine. For future updates, be specific about what changed so users know what to expect.
Once your closed testing period is underway, you can track your progress directly from the Dashboard. Under the Production section, Google clearly shows you which requirements have been met and which are still pending:
You can see exactly how many days your testers have been continuously opted in. The Apply for production button stays grayed out until all three requirements are fully met. Once the 14-day period is complete and all checkmarks are ticked, the button becomes active and you can click Apply for production.
Google will then ask you a few questions about your closed test and your app. Keep your answers clear and accurate. After submission, Google reviews your application — this typically takes a few days. You will receive an email once a decision has been made.
Once production access is granted, go to Test and release → Production, create a new release, upload your signed AAB, add your release notes, and roll out to production. Google runs a final review before your app goes live — for most apps this takes a few hours but can take up to 7 days in some cases.
Going through the entire Play Store submission process for the first time takes real effort. Setting up the store listing, generating proper screenshots, finding 12 testers, managing the 14-day testing period, completing all the declarations, and then navigating the production access application — it is a lot to handle, especially if publishing an app is not your core focus.
Appilix offers a complete app publishing service that takes all of this off your plate. You only need one thing — a verified Google Play Developer account. The Appilix team handles everything else:
If you just want your app live on the Play Store without spending days figuring out the process, this is the straightforward path. Get in touch with the Appilix team at appilix.com to get started.
There is a one-time registration fee of $25. Once paid, your account stays active permanently and there are no annual renewal fees. You can publish unlimited apps under the same account.
For most apps, the review takes anywhere from a few hours to 7 days. If your app is in a sensitive category — finance, health, or apps targeting children — it may take longer. You will receive an email notification once the review is complete either way.
Yes. You can add in-app purchases to a free app at any time after publishing. What you cannot do is change a free app to a paid app once it is live. If you want to monetize through a one-time purchase price, that decision needs to be made before your first release.
Google will send you an email explaining the reason for the rejection. Read it carefully, fix the specific issue mentioned, and resubmit. Most first-time rejections are straightforward to resolve — common reasons include incomplete declarations, a mismatched privacy policy, or a category that does not match the app's content.
Yes. You can push updates at any time by creating a new release in the Production track and uploading a new signed AAB. Each update goes through a review process but it is usually faster than the initial review. Make sure you increment your app's version number with each update.
Yes. Google requires a privacy policy for all apps on the Play Store regardless of whether your app collects user data or not. It needs to be hosted on a publicly accessible URL and accurately reflect your app's data practices.
Appilix can help. Let's start!
