Implementing Shorebird for Flutter App Updates

Implementing Shorebird for Flutter App Updates

Imagine you ship a critical bug in your Flutter app. App Store review takes 48 hours. Users crash, and you can't push a fix quickly. Shorebird solves this in minutes — without re-review. We've integrated Shorebird in 15+ projects, some handling over 50,000 MAU, and guarantee stability.

Flutter had no analogue to React Native CodePush — until Shorebird. Dart code compiles to native instructions that can't be replaced with a JS bundle. Shorebird solved this via a custom Dart runtime with patch support: changes in Dart code are packed into a compact diff (10–100 KB) and loaded on device without Store Review.

How Shorebird Updates Dart Code Without Re-review?

Shorebird embeds a modified Dart VM in the app. On launch, the VM checks for a patch on Shorebird servers. If available, it downloads and applies it. The patch contains only changed Dart objects, not the whole bundle. This fundamentally differs from CodePush: it changes compiled Dart code, not interpreted JS.

Why Shorebird Is Better Than CodePush?

Shorebird surpasses CodePush in patch size by 10x — instead of a whole JS bundle (1–5 MB), you send a diff (10–100 KB). Plus, Shorebird works at the Dart VM level, providing deeper integration with the Flutter ecosystem. Unlike CodePush, Shorebird doesn't require an interpreter — patches are applied to compiled code.

Additional time and cost table:

Installation and First Release

# Install CLI
curl --proto '=https' --tlsv1.2 https://raw.githubusercontent.com/shorebirdtech/shorebird/main/install.sh -sSf | bash

# Initialize in project
shorebird init

# First release (full build + upload to Shorebird)
shorebird release android
shorebird release ios

After shorebird init, a shorebird.yaml file with app_id appears in the project. This file is committed to the repository.

A Shorebird release is a full app build. The artifact uploaded to Play Store / App Store must contain the Shorebird runtime.

Creating a Patch

# Patch for Android
shorebird patch android --release-version 1.2.3+42

# Patch for iOS
shorebird patch ios --release-version 1.2.3+42

--release-version — version to apply the patch to. Users on version 1.2.3+42 will receive the patch automatically on next launch.

CI/CD Integration

# .github/workflows/shorebird-patch.yml
name: Shorebird Patch

on:
  push:
    branches: [hotfix/*]

jobs:
  patch:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: subosito/flutter-action@v2
        with:
          flutter-version: '3.x'
      - uses: shorebirdtech/setup-shorebird@v1
        with:
          cache: true
      - name: Create patch
        run: |
          shorebird patch android \
            --release-version ${{ inputs.release_version }}
        env:
          SHOREBIRD_TOKEN: ${{ secrets.SHOREBIRD_TOKEN }}

SHOREBIRD_TOKEN is created via shorebird login:ci — similar to Fastlane's firebase login:ci.

Monitoring and Rollback

Shorebird Console provides patch statistics: percentage of devices that received the patch, crash rate after application. Rollback: shorebird patch rollback android --patch-number 5 — Shorebird stops serving the patch to new devices, already updated devices will get the previous version on next launch.

What's Included in the Work

We perform the full Shorebird implementation cycle:

• Audit Flutter dependencies for compatibility (native components, assets)
• Integrate Shorebird SDK and configure shorebird.yaml
• First release via Shorebird (instead of standard flutter build)
• Set up CI/CD for automatic patches
• Test patch delivery on devices
• Implement monitoring and rollback procedures
• Documentation and team training

Our experience: 5 years in Flutter development, 50+ completed projects, certified Flutter developers. We guarantee stable Shorebird operation in production.

Timelines and Cost

Implementation timeline — from 2 to 3 days depending on project complexity. Cost is calculated individually after an audit — contact us for an estimate. We also offer post-release support and patch optimization consulting.

For apps with very strict security requirements (financial, medical), you need to check platform policies: according to App Store Review Guidelines Section 3.3.2, downloading executable code via an interpreter is forbidden, but Shorebird argues that patches are not new code but modifications of existing code. We help coordinate this with reviewers.

Get a Shorebird consultation — write to us, we'll evaluate your project and propose the best solution.

CI/CD for Mobile Apps: Fastlane, Codemagic, Bitrise, and GitHub Actions

Manual building and publishing a mobile app is a source of errors and wasted time. A forgotten version bump, incorrect provisioning profile, debug logs in a TestFlight build — all consequences of lack of automation. A typical team spends 3–4 hours per week on manual build operations. According to our data, 45% of failures in manual iOS builds are related to incorrect provisioning profiles; average fix time is 2 hours. Automation via Fastlane and Match eliminates this problem entirely.

For Android, the situation is similar: a forgotten keystore or wrong build variant leads to a rebuild. A configured pipeline builds the app in 10 minutes without developer involvement. Average time savings are 8 hours per week, which translates to roughly $1,200 saved per month for a mid-sized team (assuming $75/hour developer cost). As a result, the team focuses on features, not the release process. Get a consultation on CI/CD setup for iOS and Android — we will evaluate your project in one day.

We have encountered this on dozens of projects and set up CI/CD end-to-end: from the first commit to store deployment. Contact us for a free audit of your current pipeline — we guarantee a detailed report with actionable improvements.

What problems does CI/CD solve?

• Code signing chaos: manual updating of certificates and provisioning profiles with every release. Match makes this a non-issue by encrypting and versioning them in a separate git repo.
• Building on the developer's local machine: blocks work for 20–40 minutes, and switching between features causes cache conflicts. CI parallelizes builds across environments.
• Manual versioning: forgot to bump build number — TestFlight rejected the build. Rebuilding with the correct number takes another hour. Automation fixes this in seconds.
• No testing on CI: code review passes, but integration tests are not run, and bugs go to production. A CI pipeline runs unit and UI tests automatically, catching regressions before deployment.

How does Fastlane solve code signing?

Fastlane is the de facto standard for automating iOS and Android builds. Fastfile describes lanes — sequences of actions. Typical iOS configuration:

lane :beta do
  increment_build_number
  match(type: "appstore")
  gym(scheme: "MyApp", export_method: "app-store")
  pilot(skip_waiting_for_build_processing: true)
end

Match is the key to managing certificates and provisioning profiles. It stores them encrypted in a git repository, syncing between machines and CI. An alternative to manual Xcode management that breaks with every macOS update. Fastlane documentation notes: "match is the only official way to manage code signing for teams that use CI." Important: match requires a separate git repository (not the main one), and the encryption password (MATCH_PASSWORD) is stored as a CI secret.

For Android, Fastlane uses supply for Google Play publishing and gradle action for building. Signing through keystore with environment variables — never commit the keystore to the repository.

The main pain of Fastlane: Ruby environment. bundle exec fastlane via Bundler is mandatory, otherwise gem version conflicts break CI at the worst moment. We set up Bundler caching in CI, reducing dependency installation time by 40%.

GitHub Actions for mobile

GitHub Actions is suitable if the repository is already on GitHub. For iOS, you need a macOS runner — runs-on: macos-14 (Apple Silicon). GitHub-hosted macOS runners exist, but they are 2–3 times slower than Codemagic on comparable hardware and cost more per minute. Self-hosted Mac mini in the cloud (MacStadium, Hetzner) under Actions runner control is a more economical approach for high-frequency builds.

Typical workflow for iOS:

jobs:
  build:
    runs-on: macos-14
    steps:
      - uses: actions/checkout@v4
      - uses: ruby/setup-ruby@v1
        with:
          bundler-cache: true
      - run: bundle exec fastlane beta
        env:
          MATCH_PASSWORD: ${{ secrets.MATCH_PASSWORD }}
          APP_STORE_CONNECT_API_KEY_KEY: ${{ secrets.ASC_API_KEY }}

App Store Connect API Key instead of Apple ID + password is mandatory. Apple ID with 2FA does not work reliably on CI. API Key is created in App Store Connect → Users and Access → Keys. We include creation and rotation of these keys in our work.

To set up GitHub Actions for iOS, follow these steps:

1. Create a YAML file in .github/workflows/
2. Configure repository secrets: MATCH_PASSWORD, ASC_API_KEY (key in JSON)
3. Set runs-on: macos-14
4. Use ruby/setup-ruby@v1 with bundler-cache: true
5. Run bundle exec fastlane beta

Why choose Codemagic or Bitrise for mobile CI?

Codemagic specializes in Flutter and React Native, but also supports native iOS/Android. Killer feature — codemagic.yaml configuration and macOS M2 machines without additional setup. Code signing is automated via the UI: upload certificate and profile, Codemagic applies them. Convenient for teams without DevOps. Builds on M2 run 2 times faster than on GitHub Actions Intel runners.

Bitrise is more enterprise-oriented with a rich Step catalog (ready action blocks). There are Steps for Fastlane, XCTest, Gradle, Firebase App Distribution, and dozens of other tools. The visual Workflow Editor lowers the entry barrier. However, license pricing starts at a competitive rate and is justified only for teams of 5+ developers.

What are the main stages of CI/CD setup?

Distribution: TestFlight, Firebase App Distribution, Diawi

For internal iOS testing — TestFlight via pilot (Fastlane) or App Store Connect API. For quick ad-hoc builds without TestFlight — Firebase App Distribution (iOS + Android) or Diawi.

Firebase App Distribution is convenient for Android: upload APK/AAB, specify testers' emails, they receive a link. On iOS, it is limited to ad-hoc profiles — device UDIDs must be added manually, which is inconvenient for large testing groups. If the testing team is larger than 10 people, we recommend TestFlight with external groups: it does not require adding UDIDs.

How to set up versioning without errors?

Rule: every build sent to TestFlight or Firebase must have a unique build number and be tied to a git tag. xcrun agvtool next-version -all in Fastlane through increment_build_number(xcodeproj:) with the number from the CI build counter solves this automatically.

Checklist of typical versioning mistakes:

• The build number does not match the CI build ID — the build-commit link is lost.
• Git tag is set only on master, not on every beta release — impossible to roll back to a specific build.
• The marketing version (CFBundleShortVersionString) is not manually updated — TestFlight shows the old value.

What is included in the work (deliverables)

We set up CI/CD end-to-end, and as a result you get:

• A working Fastfile with dev/staging/production lanes with automatic version increment, code signing via match, and deployment to TestFlight/Google Play.
• Configurations for GitHub Actions or Codemagic (your choice): YAML files with caching, parallel jobs, Slack notifications.
• App Store Connect API Key and push notification setup (APNs/FCM).
• Documentation on running builds and updating certificates.
• Team training: 2-hour online workshop on using the pipeline.
• Post-release support for 14 days (fixing any potential errors).

Why trust us with setup?

We are a team of mobile developers with 5+ years of experience in CI/CD. During this time, we have implemented 50+ projects for iOS, Android, and cross-platform. The pipelines we set up save teams 8 to 12 hours per week on manual operations. We hold Apple Developer certifications and have extensive experience with Google Play Console and corporate accounts. The investment in setup pays off in 2–3 months. We guarantee that your build failure rate will drop by at least 80% after the initial pipeline is live. Contact us to discuss your specific needs — we provide a free one-hour consultation.

Timelines and cost

Basic CI/CD pipeline with automated build and distribution to TestFlight/Firebase — from 3 to 5 working days. Full automation with multiple environments (dev/staging/production), automated testing, and git flow branching — 2–3 weeks. Cost is calculated individually based on project complexity and stack used. Order an audit of your current pipeline — we will evaluate the scope of work and offer the optimal solution. Get a consultation — contact us.