CI/CD for Flutter - Build, Publish & Deploy

Build & Publish - CI/CD for Flutter

Performance Impact

Using CI/CD pipelines for Flutter apps does not directly affect app runtime performance like frame rate or memory. However, it ensures consistent builds and automated testing, which helps catch performance issues early before release. Proper CI/CD reduces human errors that might cause inefficient code or crashes, indirectly improving app stability and user experience.

Optimization Tips

To keep your Flutter CI/CD pipeline efficient and fast, use caching for dependencies like pubspec.yaml packages and build artifacts. Run only necessary tests on code changes to save time. Use parallel jobs for building Android and iOS versions simultaneously. Avoid rebuilding unchanged modules. This helps deliver updates quickly without slowing down developer feedback.

App Bundle Size and Startup Time

CI/CD pipelines can automate size checks to prevent bundle bloat by running size analysis tools on each build. This helps keep your Flutter app bundle small, typically under 20-30MB for medium apps. Smaller bundles load faster on devices, improving startup time. Automating code shrinking and obfuscation steps in CI/CD also helps reduce final app size.

iOS vs Android Differences

Flutter CI/CD pipelines must handle platform-specific steps. For iOS, you need a Mac environment for building and code signing with Apple certificates. The App Store requires signed IPA files and provisioning profiles. Android builds can run on Linux or Windows servers and require signing with your keystore. Google Play accepts APK or AAB files. Review times differ: Apple takes 24-48 hours, Google can be faster.

Store Review Guidelines

Ensure your CI/CD pipeline includes checks for compliance with store rules. For Apple, verify usage of required privacy keys in Info.plist and proper app icons. For Google Play, confirm target SDK versions and permissions. Automate screenshots and metadata uploads if possible. Always sign builds correctly and test on real devices or emulators before submission to avoid rejections.

Self-Check Question

Your Flutter app takes 5 seconds to load after a new release. What might be wrong in your CI/CD process?

• Missing performance tests or profiling in the pipeline to catch slow startup code.
• Not running code shrinking or tree shaking, causing large bundle size.
• Skipping automated tests that detect heavy widget rebuilds or blocking operations.
• Incorrect build configuration leading to debug mode release builds.

Key Result

CI/CD for Flutter automates building, testing, and deploying apps efficiently. It ensures consistent quality, reduces human errors, and helps maintain small app sizes and fast startup times. Proper platform-specific signing and compliance checks are essential for smooth app store submissions.

Practice

1. What is the main purpose of using CI/CD in Flutter app development?

easy

A. To automate building, testing, and deploying the app

B. To write Flutter code faster manually

C. To design app UI without coding

D. To run the app only on physical devices

Solution

1. Step 1: Understand CI/CD basics

   CI/CD stands for Continuous Integration and Continuous Delivery, which automates building and testing.

2. Step 2: Apply to Flutter context

   In Flutter, CI/CD runs commands like flutter pub get, flutter test, and flutter build automatically.

3. Final Answer:

   To automate building, testing, and deploying the app -> Option A

4. Quick Check:

   CI/CD automates app build and test = A [OK]

Hint: CI/CD means automate build and test steps [OK]

Common Mistakes:

• Thinking CI/CD is manual coding
• Confusing UI design with CI/CD
• Believing CI/CD only runs on devices

2. Which of the following is the correct command to run Flutter tests in a CI workflow?

easy

A. flutter test

B. flutter pub get

C. flutter build apk

D. flutter run

Solution

1. Step 1: Identify test command in Flutter

   The command to run tests in Flutter is flutter test.

2. Step 2: Differentiate from other commands

   flutter build apk builds the app, flutter pub get fetches packages, and flutter run runs the app on a device.

3. Final Answer:

   flutter test -> Option A

4. Quick Check:

   Run tests = flutter test = A [OK]

Hint: Tests run with 'flutter test' command [OK]

Common Mistakes:

• Using 'flutter build apk' to run tests
• Confusing 'flutter pub get' with testing
• Trying to run tests with 'flutter run'

3. Given this GitHub Actions snippet for Flutter CI:

steps:
  - uses: actions/checkout@v3
  - name: Install Flutter
    uses: subosito/flutter-action@v2
  - name: Get dependencies
    run: flutter pub get
  - name: Run tests
    run: flutter test
  - name: Build APK
    run: flutter build apk --release

What will happen if tests fail?

medium

A. The workflow retries tests automatically

B. APK is built regardless of test results

C. The workflow stops and APK is not built

D. Tests are skipped and APK is built

Solution

1. Step 1: Understand GitHub Actions default behavior

   If a command like flutter test fails, the workflow stops by default.

2. Step 2: Apply to given steps

   Since tests run before build, failure stops the workflow and APK build does not run.

3. Final Answer:

   The workflow stops and APK is not built -> Option C

4. Quick Check:

   Test failure stops workflow = D [OK]

Hint: Failed test stops workflow before build [OK]

Common Mistakes:

• Assuming APK builds even if tests fail
• Thinking tests are skipped automatically
• Believing workflow retries tests

4. You wrote this GitHub Actions step to build your Flutter app:

- name: Build APK
  run: flutter build apk --release
  shell: bash

But the build fails with "flutter: command not found". What is the likely cause?

medium

A. The shell should be powershell, not bash

B. The build command syntax is incorrect

C. The APK build requires emulator running

D. Flutter SDK is not installed or not added to PATH

Solution

1. Step 1: Analyze error message

   "flutter: command not found" means the system cannot find the Flutter tool.

2. Step 2: Identify missing setup

   This usually happens if Flutter SDK is not installed or its path is not set in the environment before running the build.

3. Final Answer:

   Flutter SDK is not installed or not added to PATH -> Option D

4. Quick Check:

   Command not found = missing Flutter setup = C [OK]

Hint: Ensure Flutter SDK is installed and in PATH before build [OK]

Common Mistakes:

• Blaming command syntax for 'command not found'
• Thinking shell type causes missing command
• Assuming emulator is needed for build

5. You want to speed up your Flutter CI workflow by caching dependencies. Which step should you add before flutter pub get to cache packages in GitHub Actions?

hard

A. Run flutter clean before flutter pub get

B. Use actions/cache@v3 with path ~/.pub-cache and key based on pubspec.yaml

C. Add flutter build apk before flutter pub get

D. Use actions/upload-artifact@v3 to upload pubspec.yaml

Solution

1. Step 1: Understand caching in GitHub Actions

   actions/cache@v3 caches files between workflow runs to speed up repeated steps.

2. Step 2: Apply caching to Flutter dependencies

   Flutter packages are stored in ~/.pub-cache; caching this folder keyed by pubspec.yaml hash speeds up flutter pub get.

3. Final Answer:

   Use actions/cache@v3 with path ~/.pub-cache and key based on pubspec.yaml -> Option B

4. Quick Check:

   Cache ~/.pub-cache with actions/cache = B [OK]

Hint: Cache ~/.pub-cache keyed by pubspec.yaml for faster builds [OK]

Common Mistakes:

• Running flutter clean which clears cache
• Building APK before fetching dependencies
• Uploading pubspec.yaml as artifact instead of caching