Part 3 - Publishing an Application on Google Play
- PDF for offline use:
Let us know how you feel about this.
last updated: 2016-08
Although there are many app markets for distributing an application, Google Play is arguably the largest and most visited store in the world for Android apps. Google Play provides a single platform for distributing, advertising, selling, and analyzing the sales of an Android application.
This section will cover topics that are specific to Google Play, such as registering to become a publisher, gathering assets to help Google Play promote and advertise your application, guidelines for rating your application on Google Play, and using filters to restrict the deployment of an application to certain devices.
To distribute an application through Google Play, a developer account must be created. This only needs to be performed once, and does involve a one time fee of $25USD.
All applications need to be signed with a cryptographic key that expires after October 22, 2033.
The maximum size for an APK published on Google Play is 100MB. If an application exceeds that size, Google Play will allow extra assets to be delivered through APK Expansion Files. Android Expansion files permit the APK to have 2 additional files, each of them up to 2GB in size. Google Play will host and distribute these files at no cost. Expansion files will be discussed in another section.
Google Play is not globally available. Some locations may not be supported for the distribution of applications.
Becoming a Publisher
In order to publish applications on Google play, it is necessary to have a publisher account. To sign up for a publisher account follow these steps:
- Visit the Google Play Developer Console.
- Enter basic information about your developer identity.
- Read and accept the Developer Distribution Agreement for your locale.
- Pay the $25 USD registration fee.
- Confirm verification by e-mail.
- After the account has been created, it is possible to publish applications using Google Play.
Google Play does not support all countries in the world. The most up to date lists of countries can be found in the following links:
Supported Locations for Developer & Merchant Registration – This is a list of all countries where developers may register as merchants and sell paid applications.
Supported Locations for distribution to Google Play users – This is a list of all countries where applications may be distributed.
Preparing Promotional Assets
In order to effectively promote and advertise an application on Google Play, Google allows developers to submit promotional assets such as screenshots, graphics, and video to be submitted. Google Play will then use those assets to advertise and promote the application.
A launcher icon is a graphic that represents an application. Each launcher icon should be a 32-bit PNG with an alpha channel for transparency. An application should have icons for all of the generalized screen densities as outlined in the table below:
36 x 36 px
48 x 48 px
72 x 72 px
96 x 96 px
Launcher icons are the first things that a user will see of applications on Google Play, so care should be taken to make the launcher icons visually appealing and meaningful.
Tips for Launcher Icons:
Simple and uncluttered – Launcher icons should be kept simple and uncluttered. This means excluding the name of the application from the icon. Simpler icons will be more memorable, and will be easier to distinguish at the smaller sizes.
Icons should not be thin – Overly thin icons will not stand out well on all backgrounds.
Use the alpha channel – Icons should make use of the alpha channel, and should not be full-framed images.
High Resolution Application Icons
Applications on Google Play require a high fidelity version of the application icon. It is only used by Google Play, and does not replace the application launcher icon. The specifications for the high-resolution icon are:
- 32-bit PNG with an alpha channel
- 512 x 512 pixels
- Maximum size of 1024KB
The Android Asset Studio is a helpful tool for creating suitable launcher icons and the high-resolution application icon.
Google play requires a minimum of two and a maximum of eight screen shots for an application. They will be displayed on an application’s details page in Google Play.
The specs for screen shots are:
- 24 bit PNG or JPG with no alpha channel
320w x 480h or 480w x 800h or 480w x 854h. Landscaped images will be cropped.
This is an optional image used by Google Play:
Used by the featured section of Google Play. This graphic may be displayed alone without an application icon.
- 1024w x 500h PNG or JPG with no alpha channel and no transparency.
- All of the important content should be within a frame of 924x500. Pixels outside of this frame may be cropped for stylistic purposes.
This graphic may be scaled down: use large text and keep graphics simple.
This is a URL to a YouTube video showcasing the application. The video should be 30 seconds to 2 minutes in length and showcase the best parts of your application.
Publishing to Google Play
Xamarin Studio 5.9 introduced an integrated workflow for publishing apps to Google Play. If you are using a version of Xamarin Studio earlier than 5.9, you must manually upload your APK via the Google Play Developer Console and then use the Publish to Google Play dialog for subsequent APK updates. For information about how to manually upload an APK, see Manually Uploading the APK.
In Part 2, we created a new certificate for signing Android apps. Next, we'll follow these steps to publish our app on Google Play:
Log into your Google Play Developer account to create a new project that is linked to your Google Play Developer account.
Create an OAuth Client.
Enter the resulting Client ID and Client Secret into Xamarin Studio.
Register your account with Xamarin Studio.
Sign the application with your certificate.
Publish your signed application to Google Play.
In Archive for Publishing, the Sign and Distribute... dialog presented two choices for distribution. Select Google Play and click Next:
In the Google Play API Account dialog, you must provide the Client ID and Client Secret that provides API access to your Google Play Developer account:
First, login into your Google Play Developer account. If you do not already have a Google Play Developer account, see Get Started with Publishing. Also, the Google Play Developer API Getting Started explains how to use the Google Play Developer API. Log into the API Access page on the Google Play Developer Console, accept the Terms of Service, then click Create new project:
The new API project is automatically generated and linked to your Google Play Developer Console. Next, click Create OAuth Client to associate an OAuth client with your app:
When a user requests access to their private data using your app, your OAuth Client ID is used to authenticate your app, at which time your branding information is presented to the user. The following example illustrates the kind of branding information that is required – fill in this form with information about you and your company:
Next, when the Client ID Settings dialog is displayed; click Create client:
A new Client ID is created and displayed. Click View in Google Developers Console to see more information:
The Google Developers Console provides a view of the OAuth information (Client ID and Client Secret) that is needed for completing the Sign and Distribute dialog:
Use this information to complete the Google Play API Account dialog in Xamarin Studio. You can give the account a description – this makes it possible to register more than one Google Play account and upload future APK's to different Google Play accounts. Copy the Client ID and Client Secret to this dialog, then click Register:
If the Client ID and Client Secret are accepted, a Registration Successful message is displayed. Click Next:
In the Google Play Account dialog, select a Google account and a track for uploading the application:
Google Play offers four possible tracks for uploading your app:
Alpha – Used for uploading a very early version of your app to a small list of testers.
Beta – Used for uploading an early version of your app to a larger list of testers.
Rollout – Allows you to select a percentage of users who will receive an updated version of your app; this makes it possible for you to slowly increase the percentage from say, 10% of users and increase it to 100% of users while you iron out bugs.
Production – Select this track when the app is ready for full distribution from the Google Play store.
For more information about Google Play testing and staged rollouts, see Set up alpha/beta tests.
Next, choose a signing identity to sign your app. If you have an existing signing identity, you can select Use Existing Key. If you do not have an existing key (also referred to as a certificate), see Creating a New Certificate for information about creating a new key. After you have selected a certificate to sign the application, click Next:
Finally, your app can be uploaded to Google Play. The Publish to Google Play dialog summarizes information about your app – click Publish to publish your app to Google Play:
Note that you must have at least one APK already uploaded before you can use Publish to Google Play; otherwise, you may get this error:
No application was found for the given package name. 
To resolve this error, manually upload an APK (such as an Ad-Hoc build) via the Google Play Developer Console, then use the Publish to Google Play dialog for subsequent APK updates. For information about how to manually upload an APK, see Manually Uploading the APK.
If you are using Visual Studio, you must manually upload your APK via the Google Play Developer Console. For information about how to manually upload an APK, see Manually Uploading the APK.