Publishing Android applications is the final and most exciting stage of development, which turns the written code into a product accessible to millions of users. The process of entering the market requires not only the technical preparation of the binary file, but also strict adherence to the rules Google Play Console, as well as careful attention to legal aspects. Errors at this stage can lead to account blocking or an endless cycle of refusals, so it is important to act systematically.
Modern requirements for security and code quality have made it much more difficult for beginners to enter, forcing them to reconsider the approach to assembling release versions. You will have to go through registering a developer account, preparing graphic materials, filling out metadata and, of course, the download itself Android App Bundle. Understanding each step in advance will save you time and nerves.
In this article we will analyze in detail the entire path from creating an account to the moment when your software becomes available for download. We will touch on the nuances of moderation, features of working with API levels and how to properly design a store page to maximize installation conversion.
Registration of a developer account and preparation
The first and mandatory step is to create profile in Google Play Console. For individuals, the cost of registration is a one-time fee of $25, which is paid by credit card. After payment, you will need to verify your identity by uploading a scan of your passport or driver's license, as well as filling out a tax form, even if you are not a US resident.
It is important to understand the difference between a personal and organizational account. If you are planning to scale or already represent a company, it is better to register immediately organizational profileas it requires confirmation of the organization's data (D-U-N-S number) and provides advanced access control rights for the team. A personal account has restrictions on the number of testers and access to some beta functions of the platform.
⚠️ Attention: Google has tightened the rules for new accounts. Now applications created in new profiles must undergo closed testing with a minimum of 20 testers for 14 days before they can be opened for public access.
After successful verification, a control panel will open in front of you, where you need to set up a developer profile. It is important to indicate the correct name or company name here, as this is what will be displayed under the name of your product in the store. It is also recommended to immediately link your account Google Merchantif you plan to monetize the project through in-app purchases.
Technical requirements and APK/AAB preparation
Starting August 2021, Google requires that all new applications and updates be downloaded in Android App Bundle (AAB)rather than as APK files. This format allows Google Play to optimize the size of the package downloaded by the user for a specific device, excluding unnecessary resources and libraries for other processor architectures.
When building a release version in Android Studio You must ensure that you are using a signed release key. Signature key This is a critical security element; Once you lose it, you'll never be able to update your app because Google requires all updates to be signed with the same key as the original version. It is recommended to use Google Play App Signing, transferring key management to the Google platform.
In addition to the file format, there are strict requirements for the target API level (targetSdkVersion). Currently, all new applications must be updated to the latest versions to ensure they work with up-to-date security and permissions mechanisms. Ignoring this requirement will result in automatic rejection of the build upon download. Androidto ensure it works with modern security and permissions mechanisms. Ignoring this requirement will result in the assembly being automatically rejected upon upload.
☑️ Check before downloading
It is also worth checking the application manifest for unnecessary permissions. If your application requests access to contacts or geolocation without a clear need for core functionality, this will be a reason for refusal during moderation. Use only the minimum required set permissions.
Creating an application page and filling out metadata
An application page on Google Play is your main marketing tool. It is the quality of the design that determines whether the user clicks on the “Install” button. The basis is graphic content: you will need to prepare screenshots for phones and, preferably, tablets, as well as promotional graphics.
The requirements for images are strictly regulated. Screenshots must be in PNG or JPG format, ranging in size from 320 pixels to 3840 pixels on one side. Promotional graphics (Feature Graphic) have a size of 1024x500 pixels and are displayed at the top of the page. Text on screenshots is not prohibited, but it must be readable and consistent with the interface language you specify for this locale.
| Resource type | Resolution (min/max) | Format | Note |
|---|---|---|---|
| Application icon | 512 x 512 px | PNG (32-bit) | No text and alpha channel |
| Feature Graphic | 1024 x 500 px | PNG or JPG | Do not add text on top |
| Screenshots (Phone) | 320px - 3840px | PNG or JPG | Minimum 2 pcs. |
| Video preview | 720p / 1080p / 4K | MP4 | YouTube link |
Text description is divided into a short (up to 80 characters) and full (up to 4000 characters). A short description should include USP (unique selling proposition)using keywords for SEO. A full description should detail the functionality, but avoid fluff and keyword lists, as Google's algorithms may view this as spam.
Use localization of the description and screenshots. Even machine translation of titles into major languages (English, Spanish, Chinese) can significantly increase coverage in the relevant regions.
Setting up content and age ratings
Before the application is submitted for review, you must fill out the "Application Content" section in the console menu. This stage includes completing questionnaires to determine age ratings, indicate application categories, and declare the target audience. The honesty of the answers here determines whether your product will be seen by children or whether it will be marked as adult content.
Particular attention is paid to the “Data Security” section. You must specify exactly what data your app collects (e.g. location, contacts, financial information) and for what purpose. If you use third-party SDK (for example, advertising networks or analytics), you are required to declare their behavior, since the developer is legally responsible for data leakage.
⚠️ Attention: Since 2026, Google has introduced mandatory data verification for applications with a large number of installations. If you provide incorrect data collection information, your application may be removed from the store without the right to re-publish.
You must also provide a contact email for communicating with users and a legal address (for organizations). Apps aimed at children have additional restrictions: personalized advertising and the collection of certain types of data are prohibited. Make sure you choose the right category to avoid breaking the rules Family Policy.
What is Google's Family Policy?
This is a set of strict rules for apps that target children. A violation (for example, the presence of third-party SDKs that collect data without consent, or the presence of links to social networks) leads to permanent blocking of the developer's account.
Downloading the application and starting testing
When all sections are filled out and marked in green, you can proceed to downloading. In the "Production" menu (or "Internal Testing" for starters), click the "Create a new release" button. Upload the prepared AAB file into the appropriate field. The system will automatically check the file for viruses and compliance with technical requirements.
If you have just created an account, only the “Internal testing” or “Closed testing” track will be available to you. You will need to add email addresses of testers (minimum 20 people for new accounts) and ensure their continuous participation for 14 days. Only after this will the “Extend access” button become available to enter production.
During the download process, the system may issue warnings about potential problems. For example, if the application size is too large or outdated libraries are used. Ignore these warnings you can only if you are sure that they are harmless, but it is better to eliminate them before sending them for moderation.
After successfully downloading and checking all checklists, click the "Submit for verification" button. From this moment on, your application gets into the queue for Google moderators. The status will change to “Under review”, and you will only have to wait for a decision.
Moderation process and release
Moderation on Google Play is not an instant process. Usually the verification takes from 2 to 7 days, but during holiday periods or in difficult cases it may take longer. Moderators check the application for compliance with the rules, functionality, absence of malicious code and compliance of the description with reality.
There are three possible outcomes of the test:
- ✅ Published: the application has passed the test and has become available to users (or testers).
- ⚠️ Changes required: violations were found. You will receive a detailed letter indicating the points of the rules that were violated and screenshots of the problem.
- ❌ Rejected: The application contains critical violations (for example, virus code or gross violation of intellectual property rights).
If you have received a change request, don't panic. In most cases, it is enough to correct the indicated shortcomings (for example, remove opaque text on the screenshot or add a missing privacy policy), assemble a new build with an enlarged versionCode and load it on top of the previous one. After corrections, re-verification is often faster.
The average time for first moderation for new accounts can be up to 7 days. Plan the release in advance, taking into account weekends and holidays in the USA and Europe, where moderation centers are based.
What to do if the application is blocked forever?
If an account is blocked for “Repeated violations” or “Spam”, it is extremely difficult to restore it. You can try to file an appeal through the form in the console, providing evidence that the violation was made by mistake or the account was hacked. However, if the breach is due to fraud or malware, the chances are close to zero. In this case, you will have to register a new organization with new details.
Is it possible to change the name of the application after publication?
Yes, the name of the application can be changed at any time through the "Basic information" section in the console. Changes will take effect after moderation, which usually takes several hours. However, changing your name frequently can have a negative impact on SEO and brand awareness, so do it wisely.
Do you need to pay taxes on app sales?
Google acts as a tax agent in many countries, automatically withholding VAT. However, the income you receive as a developer is your personal or corporate income, which you are required to report to the tax office of your country of residence according to local law.