The Ultimate Mobile Game Publishing Guide: App Store & Google Play Submission Checklist (2026)

Transforming a completed Unity game into a live, approved app on the Apple App Store and Google Play Store requires navigating strict technical specifications, signing certificates, privacy declarations, and store review policies.

A single missing Privacy Manifest, unhandled SDK permission, or target API mismatch can trigger immediate store rejection, delaying your commercial release by weeks.

In this guide, we provide an exhaustive 2026 engineering and publishing blueprint, detailing every step required to package, sign, submit, and optimize your Unity mobile title for iOS and Android.

1. Technical Build Requirements: iOS vs Android

Both Apple and Google enforce strict technical prerequisites for new game submissions.

2. Phase 1: iOS App Store Submission Workflow

Step 1: Certificates, Identifiers & Provisioning Profiles

1. Log in to your Apple Developer Account (developer.apple.com).
2. Create an App ID using explicit reverse domain format: com.yourstudio.gamename.
3. Enable required capabilities (In-App Purchase, Push Notifications, Game Center).
4. Generate a Distribution Certificate and link it to an App Store Distribution Provisioning Profile.

Step 2: Xcode Build & Signing Configuration

In Unity, set Build Target to iOS and export the Xcode project.

// Example: Verifying App Tracking Transparency (ATT) in iOS Unity Bridge
#import <AppTrackingTransparency/AppTrackingTransparency.h>
#import <AdSupport/AdSupport.h>

void RequestiOSATTTracking() {
    if (@available(iOS 14.5, *)) {
        [ATTrackingManager requestTrackingAuthorizationWithCompletionHandler:^(ATTrackingManagerAuthorizationStatus status) {
            switch (status) {
                case ATTrackingManagerAuthorizationStatusAuthorized:
                    NSLog(@"[ATT] Tracking Authorized");
                    break;
                case ATTrackingManagerAuthorizationStatusDenied:
                    NSLog(@"[ATT] Tracking Denied");
                    break;
                default:
                    break;
            }
        }];
    }
}

Step 3: Privacy Manifest (PrivacyInfo.xcprivacy)

Apple strictly mandates a Privacy Manifest inside your Xcode build to audit third-party SDK access to system APIs (e.g. system boot time, user defaults).

[!IMPORTANT] Ensure all third-party Unity plugins (Unity Ads, GameAnalytics, Firebase) include valid PrivacyInfo.xcprivacy files before archiving.

Step 4: App Store Connect Store Page Setup

• App Metadata: Subtitle (30 chars), Keywords (100 chars), Description.
• Screenshots: Mandatory high-resolution screenshots for 6.7-inch Display (iPhone 15 Pro Max) and 6.5-inch Display (iPhone 11 Pro Max).
• In-App Purchases: Configure IAP products and "Restore Purchases" UI button. Read our complete Unity In-App Purchases (IAP) Integration Guide →.

3. Phase 2: Google Play Console Submission Workflow

Step 1: Unity Android Build Settings

Navigate to Build Settings > Android:

1. Check Build App Bundle (.aab).
2. Under Player Settings > Other Settings:
   • Set Scripting Backend to IL2CPP.
   • Enable ARM64 target architecture.
   • Set Target API Level to API Level 34 or higher.

// Custom mainTemplate.gradle snippet for Unity Android API 34+
android {
    compileSdkVersion 34
    buildToolsVersion "34.0.0"

    defaultConfig {
        minSdkVersion 23
        targetSdkVersion 34
        ndk {
            abiFilters 'armeabi-v7a', 'arm64-v8a'
        }
    }
}

Step 2: Google Play Keystore Creation

Create a secure .keystore file in Unity via Publishing Settings > Keystore Manager.

[!CAUTION] Back up your .keystore file and passwords securely. If lost, you will be permanently unable to push game updates to existing users.

Step 3: Google Play Console Setup & Closed Testing

1. Create a new application in Google Play Console.
2. Data Safety Form: Declare all collected data points (Device IDs, Crash logs, Purchase history).
3. Closed Testing Track: Google mandates that new personal developer accounts run a closed test with at least 20 testers opt-in for 14 continuous days before requesting production access.

4. Phase 3: App Store Optimization (ASO) Strategy

A successful launch requires optimizing your store page for algorithmic discovery and conversion rate.

5. Phase 4: Production Publishing Best Practices

[!TIP] Follow these engineering guidelines to guarantee a smooth release.

1. Use TestFlight & Internal Testing First: Deploy beta builds to TestFlight (iOS) and Internal Testing (Android) before submitting for store review.
2. Configure Phased Rollouts: Enable Phased Release on iOS (staged over 7 days) and Staged Rollout on Android (10% -> 25% -> 50% -> 100%) to catch crashes before impacting your entire player base.
3. Verify HTTPS Privacy Policy Link: Ensure your studio privacy policy URL is live and mentions third-party analytics/ad services.
4. Optimize Engine Performance: Ensure rendering target is locked to 60 FPS prior to release. Read our guide on How to Optimize Unity Mobile Games for 60 FPS →.
5. Track Telemetry Post-Launch: Monitor D1/D7 retention with the GameAnalytics Unity SDK →.

🎮 Shipped Mobile Games & Official Store Profiles

Explore live commercial titles built with Unity and published across official app stores:

• 🍏 Apple App Store Developer Profile
• 🤖 Google Play Developer Profile

Featured Live Titles:

• Pet Hero: Animal Hospital — App Store | Google Play
• Restaurant RUSH: Idle Tycoon — App Store | Google Play
• Bird Sort Mania — Google Play | Read AI Dev Breakdown

Planning to launch a mobile game and need full build pipeline or technical submission support? Explore our 2026 Mobile Game Development Cost Guide or book an engineering consultation.