Production Track — what it is, track setup and publication in Google Play

What is Production Track?

Production Track is a distribution channel in Google Play Console that makes an app available for installation to all Google Play users. It is the final stage of publication that every Android app goes through before being released to the public.

Google Play Console provides four tracks for distribution: Internal, Alpha, Beta and Production. The first three are designed for testing with a limited audience, while Production Track is the only channel that opens the app to all users without restrictions on the number of installs or tester composition.

According to Google (2025), over 90% of apps in Google Play are published through Production Track. Each release undergoes automated and manual review for policy compliance, including requirements for privacy, security and content quality.

History of Production Track

Before 2015, Google Play did not have a track system — developers published an app directly to all users. The introduction of tracks made it possible to separate testing and production releases, reducing the number of errors in Production Track. In 2021, Google added Managed Publishing — the ability to control the timing of a release, giving developers flexibility in planning launches.

How does Production Track work in Google Play?

Production Track works through the Google Play Console publishing pipeline. The developer uploads a signed AAB or APK, fills out the store listing (rating, target audience, contacts), specifies distribution countries and submits for review. After approval, the app becomes available in the store within 2–24 hours.

Google Play Console automatically checks the binary for viruses, API violations and policy breaches. Production Track requires the app to be signed with an App Signing by Google Play key or the developer’s own key. Without a valid signature, the binary is rejected at the upload stage.

// build.gradle — signing config for Production Track
android {
    signingConfigs {
        release {
            storeFile file("release.keystore")
            storePassword "keystore-password"
            keyAlias "release-key"
            keyPassword "key-password"
        }
    }
    buildTypes {
        release {
            signingConfig signingConfigs.release
            minifyEnabled true
            proguardFiles getDefaultProguardFile("proguard-android-optimize.txt")
        }
    }
}

After publication, Production Track automatically distributes the update to users' devices via Google Play Store. The system uses staged rollout — the ability to gradually deploy, starting with 5% of the audience and increasing the percentage in the absence of critical errors.

Requirements for a Production Track release

Google Play has a number of mandatory requirements for apps before publication in Production Track. Violating even one requirement leads to rejection or blocking of the app. The policies cover privacy, security, content and technical quality.

• Privacy Policy — mandatory for apps that request personal data. The link must be provided in the store listing and accessible within the app
• API Level — targetSdkVersion must meet the latest Google requirements (Android 13+ for new apps)
• Content Rating — completed content rating by categories (violence, 18+ content, ads)
• Test Accounts — if the app requires authentication, test credentials must be provided for review
• GDPR Compliance — for distribution in the EU, proper handling of user data and consent dialogs are required

A separate requirement is Family Policy for apps targeting children. If the store listing specifies an age group of “under 13”, the app must comply with additional COPPA and GDPR-K requirements, including a ban on collecting advertising identifiers.

Differences between Production Track and other tracks

Production Track fundamentally differs from Internal, Alpha and Beta tracks in terms of audience, requirements and publication process. Test tracks allow distributing an app among a limited number of testers without full moderation, while Production Track requires passing a full Google review.

The key difference is store visibility. Apps in Production Track appear in search results, categories and recommendations on Google Play. Test versions are only available via a direct link and do not participate in organic distribution.

Setting up Production Track in Google Play Console

Setup of Production Track begins with creating a release in the “Production” section of Google Play Console. The developer specifies the app version, uploads a signed binary and fills out the store listing with information about the app. Each step requires careful verification before submission.

1. Go to Google Play Console → Select app → Production Track → Create new release
2. Upload an AAB or APK signed via App Signing or your own key
3. Specify the release name (e.g., “Version 2.5.0”) and release notes for users
4. Check the target audience, content rating and distribution countries
5. Submit for review and wait for the publication notification

After submission, Production Track goes through several stages: automated binary check, malware scanning, Google Play policy compliance verification and final publication. If a problem is found at any stage, the developer receives a notification with an error description and recommendations for fixing it.

To speed up publication in Production Track, it is recommended to check the app in advance using the Pre-launch Report in Google Play Console. The service automatically tests the app on several devices and reports compatibility, performance and security issues before submission for moderation.