Website

Generate Android app

How to generate a ready-to-publish android app build?

AppMySite enables you to create the .APK and .AAB file of your Android app build that can be directly submitted to Google Play for publishing. The AAB file is required for publishing on Google Play, while the APK file can be used for testing.

Step 1: Navigate to the Android build section

Step 2: Configure app identity

Customize your Android app’s identity settings. This section allows you to change or migrate your app’s package name and version details.

  • Migrate my live app – Enable this toggle, if you are transferring an app from another platform. Submit the following details:

    • Package name: The package name (also referred to as the application ID) of an Android app serves as a unique identifier for your app on the device and within Google Play Store.

    • Version name: The Android version name is a label assigned to identify a specific release version of your app. It plays a crucial role in differentiating releases and communicating updates to users within the Android ecosystem. If you’re migrating your app, the version number you input will be automatically incremented by 1.0.0 in the next immediate build. If your current app version is 1.2.1, the next build would be version 2.0.0. The version name will be visible to your users.

    • Version code: This whole number value represents the incremental build of your app. If you’re migrating your app, the version code you input will be automatically incremented by 1 in the next immediate build. If your current app version is 7, the next build would be version 8. The version code will not be visible to your users.

    • Key alias: Specify the Alias for the Key associated with the app you are migrating. The Alias serves as an identifier for the Key. Obtain this information from the developer or development platform you are migrating from.

    • Key password: Specify the password for the Key associated with the app you are migrating. Obtain this information from the developer or development platform you are migrating from.

    • Keystore file (.jks): Upload the KeyStore file for the app you are migrating. This file will have a .jks extension. Obtain this information from the developer or development platform you are migrating from.

    • Keystore password: Specify the password for your KeyStore. Obtain this information from the developer or development platform you are migrating from.

Obtain this information from the developer or development platform you are migrating from.

  • Customize my package details – Turn this toggle on if you want to customize your package name. Submit the following details:

    • Package name: Customise the package details as per your needs.

    • Version name: Enter the version name that you would like to give to this app build. Ensure you enter the version name in the correct format. For example: If your current app version is 1.2.1, the next build would be version 2.0.0. The version name will be visible to your users.

    • Version code: Submit the version code that you would like to give to this app build. Ensure you enter the version code in the correct format. For example: If your current app version is 7, the next build would be version 8. The version code will not be visible to your users.

Your package name must match the one in your Google Play Console for successful app submission.

Step 3: Configure app permissions

App permissions allow your app to request access to various device features such as the foreground location, background location, microphone, camera, location, contacts, and gallery.

  • Turn on the toggles for the permissions required for your app’s functionality.

  • Users will be prompted to grant these permissions when they launch the app.

  • Enable only the necessary permissions to avoid unnecessary permission requests.

Google Play enforces strict policies on app permissions. Ensure that only the required permissions are enabled and provide clear justification in your Play Store listing.

Step 4: Enable advanced features in the build

Some features require additional configuration before your app build can be generated. Follow the guides linked on the build configuration screen to configure any advanced settings.

Notification configurationSocial login configurationConfigure AdMob

Step 5: Generate your Android app build

  • Once all configurations are complete, click Build App to generate your APK and AAB files.

  • The build process may take a few minutes.

  • Once completed, the files will be available for download.

  • Test the APK file on an Android device before submitting the AAB file to Google Play.

By following these steps, you can successfully generate an Android app build and prepare it for submission to the Google Play Store.

Test your Android app on a real device before publishing to ensure it functions correctly.

PreviousCreate Google Developer AccountNextApp publishing time

Last updated

Was this helpful?