🔀 How to untangle and manage build distribution — Webinar, May 16th — Register
🔀 How to untangle and manage build distribution — Webinar, May 16th — Register

fastlane + Runway: the perfect match

fastlane is your team’s first step towards easier mobile releases, and Runway gets you the rest of the way. By integrating across all of your tools and creating a control center for the entire team, Runway allows you to make sense of and extend fastlane’s automations.

With Runway, get all the way to hands-free

You can do a lot with fastlane, but it leaves big gaps that your team has to make up for with manual busywork and careful coordination. Runway’s unique ability to run time-based and recurring automations, across all of your tools, means it can always pick up where fastlane leaves off.
Illustration of a Runway window extending out of a terminal window with code

Don't reinvent the wheel (or maintain it!)

Your team is wasting time building and maintaining fastlane “table stakes”. Instead, focus on your team’s unique fastlane scripting needs and let Runway take over the rest.
Illustration of a Runway window superimposed over a terminal window with code

“With Runway, <highlight>rather than building and maintaining custom tooling in-house<highlight>, we can focus on our core products and leverage the work of a team of experts in the mobile release space.”

Sr. Engineering Manager

Make everything fastlane does more visible to the team

Wires get crossed and issues are harder to diagnose when a lot is happening under the hood. By adding Runway on top of fastlane, you open up that black box and lay bare hidden side effects.
Illustration of an isometric cube with a terminal window with code serving as one of the faces, and a search glass hovering over

Keep your bespoke fastlane scripting

Your team is unique, with custom fastlane scripts to match. Runway plays nicely with anything you already have in place, so you won’t have to rework existing tooling. 
Illustration of a terminal window with code

How to get the most out of fastlane + Runway

Let fastlane do its thing

Keep build-related handling in fastlane. Things like signing and uploading to the stores should continue living in CI, executed using fastlane.

Leave time-based jobs to Runway

Because Runway can keep tabs on the outside world and changes over time, it can do things like create a new version in the app stores at the right moment, tag your releases when each version actually ships, and keep your team notified throughout.

Avoid recurring manual tasks

For example, if you’re always assigning beta builds to particular testers, or having to download and upload dSYMs for all of your builds, Runway is best positioned to handle that stuff.

Release better with Runway.

Runway integrates with all the tools you’re already using to level-up your release coordination and automation, from kickoff to release to rollout. No more cat-herding, spreadsheets, or steady drip of manual busywork.