Mastering Flutter App Deployment: From Dev to Play Store & App Store

So you’ve built your Flutter app—maybe with a visual builder, maybe with pure code—and it’s running beautifully on your device. Now comes the real challenge: getting it into users’ hands. The journey from development build to published app can feel like navigating a maze of certificates, provisioning profiles, and store listings. Let’s demystify the process.

The Core Challenge: It’s More Than Just Building

The fundamental gap many developers face isn’t writing Flutter code—it’s understanding that deployment is a separate discipline. Your app needs proper signing, configuration, and store-specific packaging. Whether you’re using FlutterFlow or writing everything from scratch, these steps remain essential.

Phase 1: Pre-Deployment Checklist

Before touching any store console, ensure your app is truly ready:

1. App Configuration: Update your pubspec.yaml with final metadata:

name: my_production_app
description: A fantastic Flutter application
version: 1.0.0+1

The version format is versionName+versionCode for Android and version+build for iOS. The + separates semantic version from build number.

2. Platform-Specific Setup:
   • Android: Configure your android/app/build.gradle:

android {
    compileSdkVersion 34
    
    defaultConfig {
        applicationId "com.yourcompany.yourapp"
        minSdkVersion 21
        targetSdkVersion 34
        versionCode 1
        versionName "1.0.0"
    }
    
    signingConfigs {
        release {
            storeFile file("your-upload-key.keystore")
            storePassword "your_password"
            keyAlias "your_key_alias"
            keyPassword "your_key_password"
        }
    }
    
    buildTypes {
        release {
            signingConfig signingConfigs.release
            minifyEnabled true
            shrinkResources true
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
}

• iOS: Update ios/Runner/Info.plist with proper descriptions for all permission requests, and configure your project in Xcode with your team and bundle identifier.

Phase 2: Generating Release Builds

Android APK/AAB

For the Play Store, you need an Android App Bundle (AAB):

flutter build appbundle

Common Mistake: Using APK for Play Store submissions. Google now requires AAB for new apps. The AAB generates optimized APKs for different device configurations.

iOS IPA

For the App Store, build through Xcode or use:

flutter build ipa

Critical Step: You must configure code signing in Xcode. Open ios/Runner.xcworkspace, select your target, and under “Signing & Capabilities,” ensure your team is selected and provisioning profiles are correctly set.

Phase 3: App Signing Secrets

Android Keystore

If you don’t have a signing key, generate one:

keytool -genkey -v -keystore ~/upload-keystore.jks -keyalg RSA -keysize 2048 -validity 10000 -alias upload

Protect this file with your life! Losing it means you cannot update your app. Store passwords securely—never commit them to version control.

iOS Certificates and Profiles

This is where many developers stumble. You need:

1. An Apple Developer account ($99/year)
2. A production certificate from Apple Developer Portal
3. A provisioning profile linking your certificate to your app ID
4. The profile installed on your build machine

Phase 4: Store Listings and Submission

Play Store Preparation

1. Create a Play Console account (one-time $25 fee)
2. Prepare assets:
   • 512x512 icon
   • Feature graphic (1024x500)
   • Screenshots for phone and tablet
3. Write compelling description and privacy policy

App Store Preparation

1. Create App Store Connect entry
2. Prepare assets:
   • 1024x1024 icon (no transparency)
   • Screenshots for all iPhone and iPad sizes
3. Complete the detailed questionnaire about data collection

Phase 5: The Submission Process

Play Store Steps:

1. Create new application in Play Console
2. Upload your AAB to “Production” track
3. Complete content rating questionnaire
4. Set pricing and distribution
5. Review and publish (can take hours to days for review)

App Store Steps:

1. Archive your app in Xcode
2. Validate the archive
3. Distribute to App Store Connect
4. In App Store Connect, add build to your app version
5. Submit for review (typically takes 24-48 hours)

Common Pitfalls and Solutions

“My iOS build fails with code signing errors” Double-check: Are your certificates installed in Keychain Access? Does your provisioning profile include the device you’re testing on? In Xcode, try Product → Clean Build Folder and rebuild.

“Play Store rejects my AAB” Ensure your android/app/build.gradle has minSdkVersion set to at least 21, and you’ve declared all necessary permissions in AndroidManifest.xml.

“App crashes on launch in release mode” Test with flutter run --release locally first. Add proper error handling and consider using flutter build apk --split-per-abi to test on physical devices before store submission.

“Missing 64-bit support” (Android) Flutter has included 64-bit support for years, but ensure you’re not using old plugins that might lack it. Run flutter build appbundle and check the output contains both armeabi-v7a and arm64-v8a.

Post-Submission Mindset

Once submitted, don’t just wait. Prepare your first update! You’ll inevitably find small fixes needed. Set up crash reporting with firebase_crashlytics or sentry_flutter:

void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await SentryFlutter.init(
    (options) => options.dsn = 'YOUR_DSN',
    appRunner: () => runApp(MyApp()),
  );
}

Deployment isn’t a one-time event but a skill you’ll refine with each release. Take detailed notes of your process, save all credentials securely, and remember: every published app started with someone figuring out these exact steps. Your app deserves to be out in the world—now you have the map to get it there.