


.png)

Start by mapping every manual step between code merge and users downloading an update, including branch cuts, version bumps, build triggers, store submissions, rollout progression, monitoring, and notifications. Each one is a candidate for automation. You can then connect Runway to your existing CI/CD, app stores, and monitoring tools to automate that entire sequence in one configured workflow. No manual handoffs, no steps that only one engineer knows how to do.
Yes. Runway's custom workflow builder, Flightpaths, lets you define exactly which steps run, in what order, with what conditions. That includes automated actions, health checks (crash rate thresholds before a rollout advances), human approval gates, custom scripts, and webhooks. Your actual release process lives in Runway, not a wiki.
Runway automates the entire release process for both iOS and Android in one workflow: branch cuts, version bumps, app store submissions, rollout progression, crash monitoring, and stakeholder notifications. Configure it once and every release runs the same automated sequence without anyone babysitting it.