The latest version of Google Play Developer App Release Steps Tutorial in 2025

In recent years, the Google Play Console system has been frequently upgraded, causing some developers to be confused about the App submission review process. This tutorial is the latest version of the Google Developer App release process in 2025. It is recommended that relevant teams save it for future use! Due to the large number of process screenshots, it is impossible to take into account every detail. Please refer to the text annotations of the relevant pictures for details.

Reference link for the Enterprise Developer Account Registration Tutorial: New Version of Google Developer Organization Account Registration, D-U-N-S Number Verification, and Payment Information Verification Real-name Process

For the specific process of App release, please refer to the following steps. If you have any questions, you can pay for consultation.

First, enter the Google Play Console backend and click “create app” to start creating an app, as shown in the figure below

Follow the prompts to enter the detailed information of the App to be released. Fill in the app name, application type, and whether it is charged according to the actual situation.

Remember to check the “Developer Program Policies” and “Play App Signing“ at the bottom, and click “create app” after checking that all information is filled in correctly, as shown in the figure below

Click “View tasks”, set the App to be released, and complete the App details.

As shown in the figure below, complete each item in the list according to the prompts. Here we will not give examples one by one. You can fill it out according to the actual situation.

The remaining graphic and text annotations are in Chinese and are for reference only.

The completed project settings will be automatically marked and checked, as shown in the figure below.

After the App settings are completed, answer questions about each type of user data and click “Next”.

There are many details to pay attention to when filling in the data security form. Information errors here will cause the App review to be rejected or removed. Click “Next” to fill in the next information.

There are many items that need to be filled in the data security form. We check them according to the actual application and business situation. I will not elaborate on each item here.

Details that need to be paid attention to, the “personal info” that the App needs to collect must be completely selected.

To avoid the App being rejected or removed, fill in the data security form accurately. Each completed item will be marked and checked, as shown in the figure below.

Next, set the “App category” according to the actual situation.

Create default store listing. Set the app name according to the prompts, briefly describe and introduce the app.

For “Feature graphic”, upload the corresponding material picture of the App.

The first quarter of the process is the most task-intensive. After the App settings and data security forms are completed, we click “create a new release”.

For App bundles, click to upload the .aab format package, as shown below

Click “Go to overview” and confirm the release for review, which means that all release tasks have been completed.

The status of the initial submission for review is “draft”. As of 2025, the normal review period for new accounts is 2 working days, and it will exceed the time limit (1-4 weeks) in special circumstances and special periods.

The above process is the release process of ordinary APPs. Special types of APPs require the completion of corresponding additional form settings (such as health applications, financial applications, etc.). If you have more questions or needs about app release, you can pay for consultation.