Viewing profile — gsavit

My team and I built this! We're mostly former mobile engineers and we’ve felt the pain of app disaster scenarios in prod firsthand. No matter how extensive our test coverage, no ma…

My team and I are mostly former mobile engineers and we’ve felt the pain of app disaster scenarios in prod firsthand. No matter how extensive our test coverage, no matter how thoro…

Or Runway will take care of the piping! Integrations with PagerDuty et al are certainly on the roadmap :)

Post-release monitoring and metrics is definitely an area of big interest for us as well! We’re excited to flesh out that part of the platform. Also the idea of release-to-release …

We're happy to hear this sounds appealing even in a non-mobile context! While some of the friction and pain points that Runway aims to solve are especially acute for mobile, it's t…

I think it's a good point. Down the road it could be smart to explore an expanded idea of release defaults and the ability to assume away new questions about edge cases that show u…

Runway doesn't actually rely on fastlane, we're interacting directly with the App Store Connect API. So, to the extent Apple avoids breaking things on their own API, Runway should …

Some aspects of mobile (e.g. deploying binary, dealing with app stores) make it a more gated and complicated process. That, coupled with our team's domain experience in mobile, led…

It's definitely a problem area that's currently tricky to tackle properly for all but the largest of teams/orgs. Building in-house is often a luxury, and one which requires a big i…

Interesting question :) Our "full autopilot" mode isn't yet launched but once it is, if you have a recurring cadence set up with scheduled kickoff and submit days, and if each rele…

We were super excited by the Xcode Cloud announcement! It’s a neat evolution of the Apple dev ecosystem and could be especially helpful for smaller teams wanting to more easily and…

Based on what we've heard from agencies, it seems it could be driven from either side: sometimes the agency handles the tooling and that's actually some of their value-add (having …

You're definitely right, in its current form Runway is aimed most squarely at mid to large sized teams. But, we do think there's still value for smaller teams - and in fact, a coup…

We started with some napkin math, graduated to a complicated spreadsheet, and then tried to distill that into this rough calculator: https://runway.team/release-cost-calculator . G…

Hi HN! I’m Gabriel, one of the co-founders of Runway ( https://runway.team ). We’re building a SaaS platform that makes it easier to coordinate your team’s mobile app releases. Run…

Right now the focus is on public/prod deployment. Beta Testing is a step within Runway, but it's not so fleshed out and no integrations are pulled in there yet. It's definitely on …

Part of what we’re trying to do with Runway is to consolidate all the various sources of information about your release. We do currently notify your team in Slack of any changes to…

Yep, we realized early on that this is a challenge. Does Runway try to be more of a plug-and-play solution for teams that need to get a basic release pipeline spun up quickly, or d…

The short answer is that we're working hard to make Runway as adaptable as possible to the varied needs that we've heard about from our partner teams. But in general - it is tricky…

We're aiming to offer release-based metrics that are hard to find elsewhere. Things like the time it took for a given release cycle, frequency, finding and displaying common releas…

We've heard from teams working on non-mobile platforms that they share a lot of these pain points. There's also the reality that coordinating app releases often includes wrangling …

Runway definitely works without CI integrated! But, lack of build data does limit some of the cool stuff Runway can otherwise do - e.g. automatically tagging releases, and soon eas…

Thanks for the kind words! We do support Bitrise! And CircleCI, GitHub Actions, GitLab CI, and Jenkins. We're adding more integrations regularly, and we prioritize as we hear from …