From Upload to Production: Android App Release Pipeline

The Modern App Publishing Journey

Publishing an Android app is no longer a one-click process. Google has instituted a strict release pipeline designed to catch bugs, privacy violations, and spam before it hits the public storefront.

Here is the exact journey your app must take.

Phase 1: Internal Testing (Optional but Recommended)

Before you invite outside testers, you should use the Internal Testing track.

• Speed: App bundles uploaded here bypass rigorous review and are available to your internal team within minutes.
• Purpose: Use this to verify that the app doesn't crash on startup and that your API keys (like Firebase or AdMob) are configured correctly in the release build.

Phase 2: Closed Testing (The Mandatory Gate)

Once the app is stable, you promote the release to the Closed Testing track.

• The Review: Google will review the app for policy compliance (usually takes 1-7 days).
• The Test: You must invite 12 independent testers who must engage with the app for 14 continuous days.

Phase 3: The Production Application

After the 14 days, you do not automatically go to production. You must apply for access by answering a detailed questionnaire about your testing methodology and the feedback you received.

Phase 4: Open Testing vs Production

Once Google approves your application, you have two choices:

Open Testing

Release the app publicly on the store with an "Early Access" or "Beta" tag. Users can download it freely, but cannot leave public reviews. This protects your app's rating while you iron out final bugs.

Production

Full release. The app is publicly indexed, users can leave reviews, and your launch is official.