Distributing your app

Google Play Publishing

Step-by-step guide to publishing a MeDo-generated Android app on Google Play, from account preparation and store listing to testing and release.

Updated 2026-09-14

#Prerequisites

Prepare the following before creating a release in Google Play Console:

• A Google account and a Google Play developer account. Google charges a one-time registration fee.
• A valid payment method and the identity or organization information required for account verification.
• A signed Android App Bundle (AAB) for a new Google Play app. Use an APK for local installation or an existing workflow only when Google Play permits it.
• A 512 × 512 px app icon, a 1024 × 500 px feature graphic, and at least two representative phone screenshots.
• A public privacy policy URL that accurately describes the app's data collection, use, storage, sharing, and deletion process.
• An app name, a short description, a full description, release notes, and a support email address.

#Confirm the package name

Find the Application ID, also called the package name, in the Android project or packaging configuration before you create the store listing.

• Use reverse-domain notation, such as com.company.appname.
• The package name permanently identifies the app on Google Play and cannot be changed after publication.
• Confirm that the package name in Play Console exactly matches the uploaded build.

#1. Register and verify the developer account

1. Open Google Play Console and sign in with the account that will own the app.
2. Create a personal or organization developer account and provide the requested contact and payment information.
3. Accept the Google Play Developer Distribution Agreement and pay the registration fee.
4. Complete identity and contact verification before creating a production release.

Keep the account owner, support email, and public developer details current. Google may block publishing until required verification is complete.

#2. Create the app in Play Console

1. Select Create app in Play Console.
2. Enter the app name and default language.
3. Choose whether it is an app or game, and whether it is free or paid.
4. Complete the initial declarations and create the app.
5. Add the app category, support email, website, and other contact details.

Choose the package name and pricing model carefully. Some identifiers and pricing changes are restricted after publication.

#3. Build and verify the release in MeDo

1. In your Mobile project, click Export installation package at the top of the editor and stay on the Android app tab.
2. Choose AAB in the format dropdown, click Packaging V… version, and confirm the 300-credit charge. Wait a few minutes, then download the .aab file from the build list.
3. Before you upload it, build an APK of the same version as well and install it on a real Android phone to check the app works — see Android: get your app on a phone.
4. Check the current Google Play target API level requirements before building the final release.

Google Play requires new apps to be uploaded as an Android App Bundle (AAB). The APK format is for direct installation and for stores that accept it.

#4. Configure the store listing

Complete the main store listing with accurate content that matches the released app.

Do not use screenshots, descriptions, or graphics that imply features the submitted build does not provide.

#5. Complete policy and app-content declarations

Before submitting a release, complete every required item in Policy and programs or App content:

• Privacy policy and Data safety — Declare all data collected or shared by the app and its third-party SDKs.
• Data deletion — Provide the required deletion method or request path when users can create accounts or the app handles personal data.
• App access — Supply review credentials and instructions if any functionality is restricted by login or membership.
• Ads — Declare whether the app contains advertising.
• Target audience and content — Select the intended age groups and comply with the Families policy when applicable.
• Content rating — Complete the IARC questionnaire accurately.
• Permissions and sensitive APIs — Explain sensitive permissions and request only what the app needs.

The declarations must match both the submitted build and the published privacy policy.

#6. Create and test the release

Choose a release track based on the current stage:

For the selected track:

1. Create a new release and upload the signed AAB.
2. Review any Play Console warnings or errors.
3. Add localized release notes where needed.
4. Save the release, review the changes, and submit it to the selected track.
5. Promote a tested release to production only after critical flows work on real devices.

#7. Submit, review, and monitor

• Use Publishing overview to confirm that the store listing, app content, countries or regions, and release are ready.
• Submit the changes for review and allow sufficient lead time. Reviews can take longer for new accounts, sensitive permissions, or complex apps.
• If Google rejects the release, address the specific policy or technical issue before resubmitting.
• After launch, monitor Android vitals, crashes, ANRs, reviews, and staged-rollout metrics.
• Keep the target API level, dependencies, privacy policy, and Data safety declarations aligned with future releases.

#Official resources

• Create and set up your app
• Target API level requirements
• Android App Bundles
• Google Play Developer Policy Center
• Google Play Academy