How to Create and Publish Apps on Google Play Console: The 2026 Developer Blueprint

The New Landscape of Google Play Console Publishing

Publishing an Android application on Google Play has evolved significantly. Google enforces rigorous developer verification including DUNS (Dun & Bradstreet) numbers for organization accounts, mandatory 14-day closed testing with at least 20 opted-in testers for personal developer accounts created after November 2023, and strict Android 14+ (Target SDK 34/35) compliance.

At JMD WORLD, having successfully published and scaled over 20+ production applications, we have codified the complete end-to-end publishing pipeline into this definitive guide.

Phase 1: Setting Up Your App in Google Play Console

1. Sign in to your Google Play Console developer account.
2. Click the blue Create App button in the upper right.
3. App Details:
   • App Name: Up to 30 characters. Avoid keyword stuffing or spammy emojis.
   • Default Language: e.g., English (United States) or English (India).
   • App or Game: Select the accurate binary type (cannot be changed easily later).
   • Free or Paid: Note that once an app is marked Free, you cannot make it a Paid download later.
4. Accept the Developer Program Policies and US export laws checkboxes, then click Create app.

Phase 2: App Content & Policy Declarations (Zero Rejections Checklist)

Navigate to Policy > App content in the left sidebar. Complete all mandatory declarations:

• Privacy Policy URL: Must be hosted on a live, publicly accessible SSL domain (e.g., https://jmdworld.in/privacy-policy.php). It must explicitly disclose permissions requested, data collected, third-party SDKs (AdMob, Firebase), and data retention policies.
• Ads Declaration: If your app includes AdMob banners, interstitials, or rewarded ads, check "Yes, my app contains ads".
• App Access: If any part of your app requires a login, provide active test credentials (username and password) so Google reviewers can test your app.
• Target Audience & Content: If targeting users under 13, you must comply with COPPA regulations and Google Families Policy. If your app is not intended for children, select ages 18+.
• Data Safety Section: Accurately disclose all data collected (e.g. Device ID, Location, Analytics, Crash logs) and whether data is encrypted in transit.

Phase 3: Mastering the 20-Tester 14-Day Closed Testing Requirement

Personal developer accounts must run a closed test with at least 20 testers opted-in for 14 continuous days before requesting production access:

1. Go to Testing > Closed testing > Click Manage track for Alpha or create a custom track.
2. Create Email List: Create an email list containing at least 25 to 30 Gmail addresses to account for non-responders.
3. Build Release: Upload your signed Android App Bundle (.aab).
4. Share the Opt-In Link: Once the closed testing track is approved by Google, distribute the web or Android opt-in link to your testers.
5. Continuous Engagement: Testers must keep the app installed and actively test features during the 14-day window.

Phase 4: Generating a Release Signed App Bundle (.aab)

Inside Android Studio, configure your release signing keystore inside app/build.gradle.kts:

android {
    signingConfigs {
        create("release") {
            storeFile = file("../keystores/release.jks")
            storePassword = System.getenv("KEYSTORE_PASSWORD")
            keyAlias = "jmdworld_release"
            keyPassword = System.getenv("KEY_PASSWORD")
        }
    }
    buildTypes {
        release {
            isMinifyEnabled = true
            isShrinkResources = true
            proguardFiles(getDefaultProguardFile("proguard-android-optimize.txt"), "proguard-rules.pro")
            signingConfig = signingConfigs.getByName("release")
        }
    }
}

Generate your bundle via terminal: ./gradlew bundleRelease. Locate the app-release.aab artifact inside app/build/outputs/bundle/release/.

Phase 5: Store Listing Assets & Production Rollout

Provide high-resolution visual assets under Store presence > Main store listing:

• App Icon: Exactly 512x512 PNG, up to 1MB.
• Feature Graphic: Exactly 1024x500 JPG or 24-bit PNG.
• Phone Screenshots: At least 4 high-resolution screenshots (minimum 1080x1920 recommended) depicting actual in-app UI.

Once your 14-day closed testing concludes, submit your answers to the production survey questions and click Apply for production. Review typically takes 2 to 7 business days.