gsavit

6 ms·

1.
by gsavit 3y ago
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 matter how thorough our QA, no matter how much we put beh
2.
Mobile App Rollbacks(runway.team)
7 points by gsavit 3y ago|1 comments
3.
Show HN: App review times, updated live from real data(runway.team)
8 points by gsavit 5y ago|0 comments
4.
by gsavit 5y ago
Or Runway will take care of the piping! Integrations with PagerDuty et al are certainly on the roadmap :)
5.
by gsavit 5y ago
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 intelligence, so your team can see how things track over tim
6.
by gsavit 5y ago
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 true that releases are often a problem area for web
7.
by gsavit 5y ago
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 up in the flow. For now, we're committed to having
8.
by gsavit 5y ago
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 remain operational! In terms of config and checkbo
9.
by gsavit 5y ago
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 us to focus there to start with. But you're total
10.
by gsavit 5y ago
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 investment not just up front but into the futu
11.
by gsavit 5y ago
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 release's interim steps/gates are green
12.
by gsavit 5y ago
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 quickly level-up their Apple DevOps. We more or less see it
13.
by gsavit 5y ago
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 everything in place already), sometimes it's
14.
by gsavit 5y ago
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 couple of our early customers are on the smaller side.
15.
by gsavit 5y ago
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 . General idea was to capture the cost of waste
16.
Launch HN: Runway (YC W21) – Easier iOS and Android app releases for teams
93 points by gsavit 5y ago|30 comments
17.
by gsavit 5y ago
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 our roadmap though - we want to help teams co
18.
by gsavit 5y ago
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 your review status in App Store Connect. Providing further
19.
by gsavit 5y ago
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 does it focus more on flexibility for more established teams
20.
by gsavit 5y ago
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, and I think the perfect balance changes dependin
21.
by gsavit 5y ago
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 release bottlenecks, and volume of blockers during testing a
22.
by gsavit 5y ago
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 dependencies on backend services. All of the above
23.
by gsavit 5y ago
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 easier/auto build selection in ASC/Play. The CI piece
24.
by gsavit 5y ago
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 teams with specific needs.
25.
by gsavit 5y ago
Hey HN, I’m Gabriel from the Runway team. We’re building a SaaS platform that makes it easier to coordinate your team’s iOS and Android releases. Hook up your existing toolchain (e.g. Jira, GitHub, Bitrise, App Store Connect, Slack), and we
26.
Show HN: Runway – Release apps with less bouncing between Jira/GH/CI/Apple/Slack(runway.team)
44 points by gsavit 5y ago|22 comments
27.
by gsavit 6y ago
My team and I have been doing some thinking on the mobile app release process. It's such a necessary part of the overall mobile development lifecycle, but it often seems overlooked: having been through hundreds of mobile releases ourse
28.
How to Ship a Mobile App(runway.team)
6 points by gsavit 6y ago|2 comments