play-store-release

Play Store Release

Release checklist — complete before every submission

1. Version management

// build.gradle.kts — increment both on every release
android {
    defaultConfig {
        versionCode = 12           // integer, must increment every upload
        versionName = "2.4.0"     // human-readable, semantic versioning
    }
}

// ✅ Automate versionCode in CI using build number
val versionCode = System.getenv("BUILD_NUMBER")?.toIntOrNull() ?: 1

2. Release build — required configuration

buildTypes {
    release {
        isMinifyEnabled = true           // required — reduces APK size
        isShrinkResources = true         // required — removes unused resources
        isDebuggable = false             // never ship debuggable release
        proguardFiles(
            getDefaultProguardFile("proguard-android-optimize.txt"),
            "proguard-rules.pro"
        )
    }
}

3. Build release AAB (not APK)

# Play Store requires AAB since Aug 2021
./gradlew bundleProdRelease

# Output: app/build/outputs/bundle/prodRelease/app-prod-release.aab

4. Target API level — must meet Play Store requirements

// Play Store requires targetSdk within 1 year of latest Android release
// As of 2025: minimum targetSdk = 34, recommended = 35
defaultConfig {
    minSdk = 24
    targetSdk = 35    // must be current — Google enforces this
    compileSdk = 35
}

5. Data Safety form — required since 2022

Required declarations in Play Console → App content → Data safety:
  - What data your app collects (name, email, device ID, etc.)
  - Whether data is encrypted in transit
  - Whether users can request deletion
  - Whether data is shared with third parties
  
Failure to complete = app rejected

6. Content rating — required for all apps

Play Console → App content → Content ratings
  - Complete the IARC questionnaire
  - Rating applies globally (ESRB, PEGI, etc.)
  - Get rating BEFORE submitting for review