Flutter
AvailableAndroid and iOS builds, with configured delivery lanes.
dart pub global activate cascade_cli cascade login cascade init
CASCADECI / MOBILE CI/CD
Build Android and iOS with GitHub Actions. Follow the outcome in one Release Control Center, from the first artifact to reported store availability.
One release. Separate platform evidence.
A successful build is a build. Store review and availability are tracked separately.
01 / THE WORKFLOW
Work in your repository. Cascade brings the setup, execution context and release evidence together.
Link your app and GitHub repository. Keep the project you already work in.
Choose Android, iOS or both. Set up the signing and destinations you need.
Push to your repository. GitHub Actions runs the configured build on hosted runners.
Use the supported lanes you have configured and authorized for your framework.
Follow execution, artifacts and reported store state in the Release Control Center.
02 / YOUR FRAMEWORK
Install the CLI for your framework, sign in and initialize from your project root.
Android and iOS builds, with configured delivery lanes.
dart pub global activate cascade_cli cascade login cascade init
React Native · Android and iOS available
npm install -g cascadeci-cli cascade login cascade init
Stable npm CLI · 0.1.0. React Native iOS distribution qualification remains incomplete; follow the guide’s platform notices.
Both CLIs use cascade. Follow the guide for PATH setup when switching frameworks.
Kotlin & Swift Planned
03 / RELEASE CLARITY
Execution and store state tell different parts of the story. Keep both in view.
Explore the documentation →Android uses Linux runners; iOS uses macOS runners. Apple membership, signing configuration and runner usage still apply.
Configure only the platforms you need. Release and signing credentials stay in GitHub Secrets; authorize integrations explicitly.
Flutter supports configured APK delivery, Play testing, TestFlight and store submission. React Native follows its verified platform setup and qualification limits.
Build, upload, processing, review, rollout and availability stay distinct. Approval alone never becomes a Live badge. Reported store state follows the dashboard’s 20-minute automatic check policy.
Structured diagnostics and linked GitHub Actions executions help you investigate build, signing, upload and submission failures.
04 / DEVELOPER EXPERIENCE
Initialize the existing project, review the generated files and diagnose setup before your first CI build.
cascade doctor
WORKFLOW CONCEPT / NOT A CONFIGURATION TEMPLATE
cascade initConnect the project and write its Cascade configuration..github/workflows/GitHub Actions provides the runners and workflow entry points.Keep generated workflow files intact. Use the guide for supported configuration changes.
CLEAR BOUNDARIES
Repository and workflow identity checks help Cascade accept results from the expected project.
Our security approach →SIMPLE PRICING
Use Cascade at no charge. Separate services used for your releases may have their own fees.
View pricing →YOUR NEXT STEP
Choose your framework and follow the setup guide, one step at a time.