Google Play Publishing#

#Prerequisites

Before publishing to Google Play, ensure you have the following ready:

• Google Play Developer Account — $25 one-time registration fee
• Privacy Policy — Publicly accessible URL required for all apps
• Data Safety Section — Disclose all data collection and sharing practices
• Content Rating — Complete the IARC questionnaire for age-appropriate classification
• Target Audience & Content — COPPA compliance if targeting children under 13
• GDPR Compliance — Required if serving users in the European Economic Area

#Get Your Package Name

Your package name (Application ID) is generated by MeDo — find it in your project settings.

• Format must follow reverse-domain notation: com.company.appname — all lowercase, dots allowed
• Once published to Google Play, the package name can never be changed — choose carefully
• The package name permanently identifies your app across all Google Play listings worldwide

#Prepare Your App

1. Generate your app using the MeDo platform — select app type and describe requirements
2. Build a signed release AAB (Android App Bundle) or APK using MeDo's one-click build
3. Verify locally — Install the release build on a real Android device and test all features
4. Ensure your app targets API level 34 (Android 14) or higher for new apps

#Configure Store Listing

#Submit for Review

1. Upload your AAB/APK to the appropriate release track — Internal testing → Closed testing → Open testing → Production
2. Complete the Content Rating questionnaire through the IARC system for all targeted countries
3. Fill out the Data Safety section with accurate information about all collected data types
4. Provide a Privacy Policy URL that is publicly accessible and accurately reflects your data practices
5. Set pricing and distribution — Choose free or paid, select distribution countries in the Pricing & Distribution section
6. Add app category, contact details, and developer website for credibility

#Review & Launch

• Submit your app for review through the Google Play Console — review the release checklist first
• Review times — New accounts: up to 7 days; established accounts: 1–3 days; updates: hours to 3 days
• If rejected — Read the detailed policy violation message, fix the issues, and resubmit the corrected build
• After approval — Publish to production and monitor the Android Vitals dashboard for crashes and ANRs
• Maintain your app — Respond to user reviews, push updates for bug fixes, and keep the target SDK current