<img src="abc.png" />
call to replace anchor tags contains '/admin' in href

Publishing Android Mobile App on Google Playstore

Register for a Google Play Developer account

To publish Android apps on Google Play, you'll need to create a Google Play Developer account.

  1. Using your Google Account, sign up for a Developer account.
  2. Once you have a Developer account, you can use the Play Console to publish and manage your apps.
  3. During the signup process, you'll need to review and accept the Google Play Developer Distribution Agreement.
  4. There is a $25 USD one-time registration fee that you can pay with the following credit or debit cards:

    • MasterCard
    •  Visa
    • American Express
    • Discover (U.S. only)
    • Visa Electron (Outside of the U.S. only)
Note: The types of cards accepted may vary by location.

     5. Type your account details. Your "Developer name" is displayed to customers on Google Play.

Upload an app

After you've signed up for a Google Play Developer account, you can create apps using your Play Console.

Create an app

  1. Go to your Play Console.
  2. Select All applications All applications > Create application.
  3. Using the drop-down menu, select a default language and add a title for your app. Type the name of your app as you want it to appear in Google Play.
  4. Create your app's store listing, take the content rating questionnaire, and set up pricing & distribution.

Get your app ready for production, alpha, or beta

The APK page is no longer available within your Play Console. To get your app ready for production, alpha, or beta, you can prepare & rollout releases to a specific track.

A release is a combination of one or more build artifacts that you'll prepare before releasing an app or update to users.

Manage APK files

Package names for app files are unique and permanent, so please name them carefully. Package names can't be deleted or re-used in the future.

1. Find your APK files.

To see your app's APKs:

  • Go to your Play Console.
  • Select an app.
  • Select Release Management Artifact library. You'll see a list of your app's draft, active, and archived APKs.
    • Draft: APKs that have not been served to users yet
    • Active: APKs currently being served to users
    • Archived: APKs that were once active but are no longer being served to users

2. APK file sizes.

APK files have a maximum file size, based on the Android version your APK supports. If you can't support all devices with a single APK, you can upload multiple APKs using the same app listing that targets different device configurations.

  • 100MB - APKs that target Android 2.3 and higher (API level 9-10 and 14+)
  • 50MB - APKs that target Android 2.2 and lower (API level 8 or lower)
Tip: Users must run Play Store version 5.2 or higher to install 100MB APKs.

3. Sign your app.

Android requires that all apps be digitally signed with a certificate before they can be installed. For more information, go to the Android Developers site.

You can sign your app from the command line using the tool apksigner or configure Gradle to sign it for you during the build. Either way, you need to first generate a private key using keytool. For example:

keytool -genkey -v -keystore myAppKey.keystore-keyalg RSA -keysize 2048 -validity 10000 -alias my-alias

Note: keytool is located in the bin/ directory in your JDK. To locate your JDK from Android Studio, select File > Project Structure, and then click SDK Location and you will see the JDK location.

This example prompts you for passwords for the keystore and key, and to provide the Distinguished Name fields for your key. It then generates the keystore as a file called,myAppKey.keystore saving it in the current directory (you can move it wherever you'd like). The keystore contains a single key that is valid for 10,000 days.

4. Upload the keystore file in the Mobile Signing keys in the StoreHippo Admin Panel. 

5. After saving the key, edit the mobile app record and select the key.
6. Rebuild the app, and it will automatically be signed with that key.