Introduction

The Mobile Fastlane Framework is a reusable, configuration-driven fastlaneopen_in_new setup. It builds, distributes and AI-tests React Native apps, as well as fully native Android and iOS apps. You drop the same Fastfile and lib/ folder into every project. All project-specific details live in YAML and environment variables, so onboarding a new app never means editing Ruby.

• Android → Gradle build (APK or AAB) → Firebase App Distributionopen_in_new, plus the optional Firebase App Testing agent for AI-driven tests on real devices.
• iOS → Xcode archive (IPA) → TestFlightopen_in_new via App Store Connect.
• Interactive CLI: fastlane init_project generates the configuration for a new project, and fastlane setup lets you pick the environment, flavor, APK/AAB and target for each run, then saves those choices as reusable profiles.
• Reporting: Microsoft Teams Adaptive Cards, Slack and HTML e-mail reports for every run.

Who this documentation is for

These pages are written for mobile and DevOps engineers who need a repeatable release pipeline. You don't need to know Ruby. If you have used Gradle or Xcode from the command line, you have enough background. Every page links to the official documentation of the tool it relies on (fastlane, Firebase, Apple, Android, GitHub), so you can check each step against the source.

Status

The 60-second tour

# 1. One-time: generate fastlane/config/environments.yml for this project
~/my-app $ bundle exec fastlane init_projectcontent_copy
# 2. Every run: choose (or reuse) a setup and build/distribute
~/my-app $ bundle exec fastlane setupcontent_copy
? What do you want to do?
❯ Use last setup (staging-aab: android · staging · AAB · distribute)
Android development configuration is valid.
Firebase App Distribution — STAGING: release 1.4.0 (57) distributed to "qa-team"
# 3. In CI: replay the same profile without prompts
~/my-app $ bundle exec fastlane run_profile name:staging-aabcontent_copy

Next steps