How to publish your app on Google Play: a complete step-by-step guide

After completing development and testing, the decisive moment arrives: publish your app on Google Play. It's when you go from compiling to winning over users, and from code to downloads real, with all that this implies at the level of records, policies, tests and review.

If it's your first time, it's a good idea to have the complete map clear: create the developer account, prepare the signed package (APK or better AAB), configure the Play Store listing with texts and resources, choose countries and price, complete classifications and, finally, submit for review. Below you will find a detailed guide that integrates the official Play Console steps and the best practices you need to avoid rejections and speed up publication.

Before you start: Prepare your project and app package

The official environment for creating apps Android is Android Studio, from where you will generate a APK or, preferably, an Android App Bundle (AAB)The recommended process is Build > Generate Signed Bundle or APK, which will allow you to sign with your certificate and ensure that only you can release updates.

To sign you need a keystore and a key (alias) with a password; Android Studio makes it easy to create both If you don't have them yet, fill in the minimum certificate information (your name is sufficient) and safely store the keystore and its passwords; you'll need them for future versions.

El package name (applicationId) is unique and permanent: it cannot be deleted or reused. In addition, each launch must increment the versionCode of your app. Keep in mind that the Play Console imposes a maximum versionCode of 2.100.000.000; if you exceed it, you will not be able to upload the bundle.

Set up Play App Signing when you create your first build: you can use a signing key generated by Google or your own key. This feature simplifies distribution and helps you protect your signature over the long term.

In terms of size, Google Play calculates the estimated download of your generated APKs from the AAB using gzip. The current limits are: 200 MB for the compressed size of each generated APK from bundles on a single device, and for older apps that still publish with a single APK, 100 MB. The bundle may be larger; Play optimizes delivery per device.

Create your Google Play developer account

To publish you need a developer account. Sign in with your Google account, accept the Developer Distribution Agreement, and pay the one-time registration fee. 25 USD. Next, fill in the details: developer name (visible to users), email, website, and postal address.

If your app is paid or includes in-app purchases, set up a payment profile to manage payments and access sales reports from the Play Console. Having your profile ready from the start prevents launch blockers and ensures monetization works from day one.

You can install Google Play on Windows 11 like this

Open Play Console and register your app

Go to Play Console and go to All Apps > Create app. Choose the default language and name your app will appear under on Google Play; you can change this later. Indicate whether it is app or game (this can be modified later) and whether it will be free or paid.

Add a contact email visible to users and complete the statements that appear during creation. Keep in mind that if your game is free, it will appear by default on both Google Play and Google Play Games on PCIf it's a paid game, you'll need to specifically list it on Google Play Games on PC for availability on that platform.

Play Store listing: store texts and resources

The Play Store listing is what users will see when they discover your app. In Product Details you must complete the name, the short description, and the full description. The official documentation specifies 30 characters for the name, 80 for the short description, and 4.000 for the full description, although you will see guides that mention up to 50 characters for the name. Take as a reference what the console itself shows you in your case.

Mind your language: Avoid repetitive or irrelevant keywords in your name or descriptions. Keyword stuffing annoys users and can carry the suspension According to the Google Play Developer Program Policies. Prioritizes clarity, benefits, and use cases.

In Graphic Resources you can upload the icon, a video and between 2 and up 8 captures per device type (phone, tablet, Android TV, Wear OS). Shows key features, real-world screens, and value streams. By posting, you grant Google a license to use these resources for promotional purposes (for example, highlighting your app on Play).

Choose category (app or game) and the appropriate subcategory, and add labels Internal features that help with the search. Age classification is completed via questionnaire, but to do so you'll need to have uploaded a package (AAB/APK), so You can leave it for after creating the version..

Provide contact information visible on the card: email is required, but you can also add web and telephone to improve support. In the console, you'll find this under Increase users > Presence in Google Play Store > Store settings.

Don't forget the Privacy policy: Include a valid and accessible URL. If the app accesses sensitive data or content on the device, in addition to linking to it in the listing, you must display it within the app itself.

Languages, translations and localization

By default, the upload language is en‑US, but you can add translations of the information (localized text and images/videos). This way, users will see the page in their preferred language, which improves conversion and retention.

If you do not provide translations, Play may display a automatic translation and highlight it on the listing, with the option to view the original language. Please note that the automatic service is not available in languages ​​such as Armenian, Romansh, Tagalog, or Zulu, so it's a good idea to plan manual localizations in target markets.

Upload your version: testing and production

To release your app, create a version from the console. You can choose internal test (private access by URL), closed test (approved testers), open test (anyone can join, with option to limit number) or production (available to all users in enabled countries). You also have the mode of previous registration to capture interest before launch.

When creating the version, upload the AAB or APK generated by Android Studio. The console automatically extracts metadata (such as the version), but you'll need to write Release Notes for each language you want to cover. Take this opportunity to share improvements, fixes, and updates.

Choose the type of publication: with the standard publication, updates are processed and published as soon as they are approved (some apps undergo extended reviews of up to seven days, or longer in exceptional cases). With the managed publication, you control exactly when changes become visible once they've been approved.

Remember that changes that require review are not automatically submitted: they are added to “Changes that have not yet been submitted for review” on the Release Summary page. You'll need to explicitly submit them when you want them to be reviewed.

Content classification and target audience

Complete the questionnaire Content Rating right after you upload your package. If your app is marked as "Unrated," it may be removed from the store. The questionnaire assesses topics such as violence, language, gambling, and more, and determines the recommended age.

Also, fill in the section of Content and target audienceThis isn't the same as a rating: here you state the age range your app is designed for and whether it's specifically geared toward children, which carries additional requirements.

Price and distribution

Decide if your app will be free or paidYou can convert a paid app to a free one later, but not vice versa. Also define the countries or regions where you want it to be available. Make sure your payment profile is up and running if you're going to charge.

Bundle management, APK and artifact explorer

Google Play uses Android App Bundles to generate device-optimized APKs. You upload a single bundle, and Play takes care of generating and distributing the appropriate APKs for each configuration, reducing download size and improving performance.

To inspect your artifacts, go to Test & Publish > App Bundles ExplorerOn that page you will find a version filter which works in conjunction with the Details, Downloads, and Delivery tabs. It's the functional equivalent of the old artifact library in the previous console.

Files may be in a state Draft (not yet published), Active (available to users) or Archived (previously active, no longer offered). Manage these statuses to keep your release pipeline organized and avoid release conflicts.

Publication statuses and reviews

The console displays several states that are worth understanding. In the Application status You can see if it is in Draft, Internal Testing, Closed Testing, Open Testing, Pre-registration, Production, No active version, Unpublished, Pulled by Google, or Suspended. These reflect the visibility and availability real.

At the update status You'll see if there are no pending changes, if they are under review, if the update has been rejected, if the app has been rejected (the latter applies to Draft apps that you are trying to publish for the first time), if there are changes not yet submitted for review, or if you are checking out a previous version.

Finally, the Item status Refers to specific parts of an update, such as a specific version or the result of a listing experiment: Draft, In Review, Rejected Update, Rejected App, Available, or Previous. Knowing the difference between a “rejected app” and a “rejected update” is key to responding appropriately.

Please note that for some developer accounts, Google may spend more time reviewing your app. protect usersThis can take up to seven days or more in individual cases. In addition, personal accounts created after November 13, 2023, must comply specific testing requirements before being able to publish.

Essential technical requirements

Each climb must increase the versionCode and not exceed the maximum of 2.100.000.000. It's good practice to plan a numbering strategy that will support your product's growth without approaching that limit.

Your app must guide a target API level that meets current Google Play requirements. These requirements are evolving to provide a more secure environment; please refer to the official documentation for the current required level and future schedule.

Good listing and ASO practices

Optimize your listing with clear headlines, benefit-oriented descriptions, and screenshots that show key functionalitiesAvoid keyword stuffing. Internal tags aid search, and translations/localizations improve conversion in international markets.

In resources, combine images and a short video real-world use if it adds value. Remember that Google may use your resources for promotional purposes, which is an opportunity to boost your app's visibility on Play and other Google services.

“Having an expert team that listens, iterates quickly and maintains a close support before and after delivery can make the difference: agile product, intuitive interface and results above expectations.”

Test Flow Tips

Take advantage of internal test to immediately validate builds with your team. Then, use closed testing with larger groups of testers and, if appropriate, an open test to gather public feedback on a larger scale before moving to production.

Manages the appropriately tester groups and version control. Document changes in the Release Notes for each language; this helps with support and gives end-user confidence.

How to create the app in Play Console, step by step summary

If you want a summary sequence: open Play Console, go to All apps and press Create app. Choose the default language and display name, select whether it's an app or game, free or paid, add your contact email address, and complete the Declarations. Finish by clicking Create App.

Afterwards, from the Control panel, the console will guide you through the key steps: store listing, content details, pre-publication management and testing, promotion, and finally, launch. You'll see indicators that will help you complete each section until you achieve your goals. green checks.

Operational notes and shortcuts in the console

To review your bundles and APKs, go to Test & Publish > App Bundles ExplorerUse the version filter and the Details, Downloads, and Delivery tabs to understand what each device type receives.

If a Error summary At the end of the release process, expand it to see recommended or required fixes. You won't be able to publish until you resolve the bugs. You can publish warnings or minor issues, although it's recommended you fix them.

Essential checklist before launching

Verify that you have completed: app versions (AAB/APK upload and notes), Play Store listing (texts and resources), content classification (questionnaire), app content (including target audience), and price and distribution (free or paid, countries).

Review policies: privacy, permissions, access to sensitive data, ads, and content. Make sure the privacy policy URL is working correctly and that the information within the app is consistent with what is stated in the console.