Publishing an Android application is the process of making a developed Android application available to users through the Google Play Store or other Android application distribution platforms.
In the process of publishing an Android application, you must first have a Google Play developer account. If you do not have a Google developer account, you can create your account by reviewing the Google Play Developer Account Creation document.
Log in to the created Google Play Developer account. The All Apps page will welcome you.
Click the Create App button at the top right of the screen.
Specify the name of your application and it will be displayed in the Play Store.
Select the languages in which the application will be used. Offering support in multiple languages can increase the reach of your application.
Select whether your app is free or paid. If paid, set pricing and free trial periods.
In the Declarations field, you must accept policies such as Developer Programme Policies, US export laws.
Then click the Create App button in the lower right corner.
In the screen that opens, Start testing now, Set up your app, Release Your App, fields must be filled in order.
1.Start testing now in the field
Select Testers, Create and Roll out release areas are included.
Select Testers:
This section is used to select test users to whom the application is accessible during the beta testing phase. By enabling your work to be tested among specific users, it supports you to collect feedback and fix bugs.
Create and Roll out release:
This section allows you to create and publish a beta or full version of your application.
The beta version is tested by specific users or through a public beta programme, while the full version makes the application available to everyone.
This section also allows you to configure the app's content, target devices, and other deployment settings.
2. Set up your app
Set Privacy Policy, App Access, Ads, Content Rating, Target Audience, News App, Covid-19 contact tracing and status apps, Data safety, Government apps, Financial features fields must be filled in Set up your app. Each sub-heading contains specific information that needs to be filled in depending on the type and requirements of your app. These settings are important to improve the user experience and security of your app and to ensure compliance with Google Play policies.
You can get the URL from within the application. On Google Play, app developers must provide a privacy policy to respect users' privacy rights.
This section requires permissions for your app to use certain APIs or services. For example, access to location data, camera usage, etc. Within this screen, select the way you want it to be based on your application.
This field is important for applications that contain advertisements. It helps you configure advertising policies, such as how adverts are served and how advertising credentials are handled.
Allows you to set the age restriction and appropriateness level of your app's content. This shows which age groups your app is suitable for.
It helps you identify the target audience and users of your app. This information can help your app get discovered.
This option contains special settings for news applications. It is useful for applications that offer news content.
COVID-19 includes special settings for contact tracing and status applications. It enables such applications to provide accurate and reliable information.
It contains policies and explanations about the data security of the application. It explains how users' personal data is processed and protected.
If you are developing an application for the government or public sector, it helps you make the relevant settings in this area.
Contains special settings related to financial transactions and payment methods. This is important for financial applications.
3. Release Your App
This is where you set the settings for the live (production) version of your application. This version is available to all users.
It is a section used to make your application open to beta testers. Here you can configure the beta version.
It is used to test your application with a limited beta test audience. Only invited users can access this version.
It allows you to offer your application as a private test version to users within your internal team or organisation.
You can use this section to convert the live version of your application to beta.
You use this section to manage your live release and control the version available to users.
Each title allows you to adjust the settings for different versions and target audience of your application. This is important for updating your app regularly and presenting it to different user groups.
After the required fields are filled in, click Production on the left panel.
On the screen that opens, click the Create new release button on the right panel.
You must add the AAB file in the screen that opens.
Release Name:
This field identifies the name of a specific version of your application. It is important to choose a unique name for each version because this name helps distinguish between versions of the application. For example, for Version 1.0.1, you might choose a name such as Update 1.0.1.
Release Notes:
This area contains important updates, changes, and notes for a specific version of the application. It is used to tell users what has changed or been added in this version of the app. It helps keep users informed about the update and motivated to update the app.
After these transactions are completed, you must perform the transactions within the Platform.
Click Config Manager view mode from Header in your application. Then name the Config manager and click the Create button.
Then click on the Android category. Activate the Android Switch.
From the screen that opens, go to the Play Store Settings area. Click ADD NEW in the Configuration pop-up window.
Give naming in Google play connect API settings. For example AAB File. Then select AAB from the Publish Type pop-up window.
If you have a signature file in the Signing Store File field in line with the selection, add the file by clicking Choose. If you do not have a Signature, you can leave the Signing Key Alias, Signing Key Password fields blank and click the Create button. Kuika will fill these fields automatically.
The setting you created will be displayed in the Configuration field with AABF.
Then click the Rocket icon, select Android from the pop-up window and click the Publish button.
Then check your e-mail.
Then click on the Main store listing field in the left panel in Google Play Console.
App Name: This is the name of your app and is visible to users.
Short Description: Short and concise application description.
Full Description: Contains a detailed description of your application.
App Icon: The icon or logo of your application.
Feature Graphic: A large graphic or banner used to promote your app.
Video (Promotional Video): Promotional video of your application.
Phone Screenshots: Screenshots of your application for phones.
7-inch Tablet Screenshots: Screenshots for 7-inch tablets.
10-inch Tablet Screenshots: Screenshots for 10-inch tablets.
Chromebook Option to indicate that you are compatible for Chromebook devices. This indicates that your app is intended for Chromebook users. This information and visuals help users discover, understand and download your app. It is important for the success of your app and the interest of your users. After entering the required fields, click the Save button.
Then click Publishing overview in the left panel. In Changes ready to send for review, click Send app for review.
Click the Send app for review button to send your app through Google's review process before publishing it to the Google Play Store. This review process is carried out to verify that your app complies with Google Play policies and does not threaten user safety.
The relevant Google team will check that your app complies with all requirements. This includes compliance with privacy policies, security measures, content restrictions and other policy requirements. The review usually takes a few days and ensures that your app can be published in the Google Play Store after approval.
After you submit your app to the review process, you will receive notification about the outcome. If your app is approved, it becomes available for download by users. However, if there are any problems, you can get feedback on warnings or corrections needed, and you can submit your app again after fixing it. This process is important to ensure that users have access to safe and reliable apps.
