Skip to content

Blog

Mobile release trains that do not break

Fastlane, staged rollouts and feature flags — a practical playbook from eighteen App Store submissions without a Friday-night rollback.

Release day should be boring

Mobile teams feel production pain differently: store review delays, irreversible user updates, and crash reports that arrive hours later. A release train turns chaos into a calendar.

The playbook

  1. Trunk-based development with short-lived branches
  2. Fastlane for signing, screenshots and TestFlight uploads
  3. Staged rollouts — 5%, 25%, 100% with crash-rate gates
  4. Feature flags for risky UI, not for broken core flows
  5. Rollback plan — previous build artifact always one click away

React Native specifics

Keep native modules documented, pin dependencies monthly, and run device farms on the two oldest supported OS versions. Most regressions we see are permission or navigation edge cases, not JavaScript logic.

When clients push for daily releases

Explain store review realities early. Internal builds can be daily; public store releases should follow the train unless you have strong automated QA and on-call coverage.

Need help stabilising mobile delivery? Reach the studio.

Blog