Cloud Management

Mobile App CI/CD Pipeline Setup for iOS and Android Teams

iJurug Soft2026-11-145 min read

A mobile app CI/CD pipeline builds, tests, signs and ships every iOS and Android release automatically, from a merged pull request to TestFlight, Google Play testing tracks and finally a staged store rollout. It removes the fragile "only one laptop can build the release" problem and makes frequent, predictable releases routine rather than stressful.

Why mobile delivery needs its own pipeline

Web CI/CD pushes a container to a server and you are done. Mobile is different in ways that catch backend-focused teams off guard:

Because of this, a generic CI/CD pipeline setup is a good base, but mobile needs extra stages on top. If your releases currently depend on one developer's machine, tell us how you ship today and we will suggest a first pipeline milestone.

Stages of a production-grade mobile app CI/CD pipeline

1. On every pull request

Run linting, static analysis and unit tests, then build a debug version of both platforms. Fast feedback here keeps the main branch healthy. Flutter teams run flutter analyze and flutter test; native teams run XCTest and JUnit or Robolectric suites.

2. On merge to main

Build signed release candidates, increment build numbers automatically, and distribute them to internal testers through TestFlight, the Play Console internal testing track or Firebase App Distribution. QA always tests the exact binary that will ship.

3. Automated UI and device testing

UI tests (XCUITest, Espresso, Flutter integration tests, or Maestro for cross-platform flows) run on emulators or a device cloud such as Firebase Test Lab. These are slower, so it is common to run them nightly or on release branches only. Our guide to mobile app testing services covers what to automate first.

4. Release and staged rollout

A tagged release uploads to App Store Connect and Google Play with release notes and metadata. Use phased release on iOS and staged rollout percentages on Play, watching crash-free sessions in Crashlytics or Sentry before widening the rollout.

Handling a bad release

Stores do not support true rollback. Your options are to halt the staged rollout, ship a fixed build quickly through the same pipeline, and switch off the affected feature with remote flags. Building feature flags in from the start is what makes this safe.

Code signing done properly

Signing is where mobile pipelines tend to break. Good practice looks like this:

Choosing your tooling

There is no single right stack. The choice depends on your framework, team and existing CI.

fastlane as the automation layer

fastlane scripts the repetitive steps: building, signing, taking screenshots and uploading to both stores. It runs on almost any CI service, which keeps you portable.

Where builds run

Over-the-air updates

React Native teams using Expo can push JavaScript-only fixes through EAS Update, and Flutter teams can look at Shorebird. Both must stay within Apple and Google store policies, which do not allow changing an app's core purpose without review, so treat them as a fast path for fixes rather than a replacement for releases.

How we set up mobile pipelines

iJurug Soft builds web and mobile apps with React, Flutter and Node, and cloud and DevOps work is part of the same practice, so the people setting up your pipeline also understand the app code. A typical engagement runs on fixed milestones: audit how you ship today, design the pipeline and signing model, build it in your repository, then hand over documentation and support the first few releases.

We also bake in store-readiness checks, such as privacy manifest and permission strings on iOS and target SDK levels on Android, which helps you avoid the issues covered in our article on app store rejection.

Frequently asked questions

Do we need a Mac to build iOS apps in CI?

Yes, iOS builds require macOS and Xcode. You can rent hosted macOS runners from your CI provider or a mobile CI service, or run your own Mac machines.

Can one mobile app CI/CD pipeline handle both iOS and Android?

Yes. Cross-platform apps built with Flutter or React Native usually share one pipeline definition with parallel jobs per platform. Native apps can do the same with separate build stages.

How long does pipeline setup take?

It depends on the number of apps, build flavors and environments, the state of your tests and how signing is handled today. We confirm a timeline after reviewing your repository.

What does it cost to set up?

We do not publish prices. Scope, existing tests, the number of build variants and whether you want ongoing support all affect effort. Share your setup and we will provide a clear quote.

Want releases that ship from a merge instead of a laptop? Describe your app, framework and current release process through our contact form, or write to info@ijurugsoft.com. A senior engineer will review it and outline the pipeline we would build with you.