Looks promising,but good luck keeping up with the appstores' unannounced changes. Btw what kind of metrics would be available for users?
Show HN: Runway – Release apps with less bouncing between Jira/GH/CI/Apple/Slack
11–20 of 23 posts
Re: Show HN: Runway – Release apps with less bouncing between Jira/GH/CI/Apple/Slack
#12The value add of workflow management and coordination beyond build-centric task automation makes sense. Excited for what it sounds like you guys have up your sleeves on the web development side also.
I'm curious how the product can effectively support unique/customized workflows across different teams? How do you guys think about that?
Re: Show HN: Runway – Release apps with less bouncing between Jira/GH/CI/Apple/Slack
#13Looks promising,but good luck keeping up with the appstores' unannounced changes. Btw what kind of metrics would be available for users?
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 and over time are a couple examples of the types of data Runway could be uniquely positioned to provide.
Re: Show HN: Runway – Release apps with less bouncing between Jira/GH/CI/Apple/Slack
#14It seems like it's going to be tricky to balance between flexibility to support all kinds of workflows and streamlined experience by standardizing workflows. Where does Runway stand in terms of this tradeoff?
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 depending on what type of a team we're talking about. We've talked to small teams, larger ones with more complex structures (like multiple product teams all contributing code to a single binary), but also teams who are fairly agnostic about their branching and tooling setup, and those who are more opinionated.
There is certainly a version of Runway that could be much more prescriptive (and limited) for teams who prefer more guidance in setting up a release toolchain. For now, we're trying to hit a sweet spot of enough flexibility to meet the needs of most teams, while encouraging best practice in a few areas that we think will streamline everyone's process.
It's an ongoing conversation and it's really helpful to hear from individual teams on how Runway could help in their specific situation.
Re: Show HN: Runway – Release apps with less bouncing between Jira/GH/CI/Apple/Slack
#15I always had trouble getting notified when a release was blocked from App Store review since it required getting an email and then logging into App Store Connect to find the reason for rejection. Does Runway help surface rejection reasons into other tools?
Re: Show HN: Runway – Release apps with less bouncing between Jira/GH/CI/Apple/Slack
#16The value add of workflow management and coordination beyond build-centric task automation makes sense. Excited for what it sounds like you guys have up your sleeves on the web development side also. I'm curious how the product can effectively support unique/customized workflows across different teams? How do you guys think about that?
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 with stronger opinions and preferences on the individual parts of their toolchain configuration?
So far we've tried to hit a balance between the two, informed as much as possible by our pilot teams and our gauge on what will most effectively serve the most teams to start. Will definitely be an ongoing conversation.
Re: Show HN: Runway – Release apps with less bouncing between Jira/GH/CI/Apple/Slack
#17I always had trouble getting notified when a release was blocked from App Store review since it required getting an email and then logging into App Store Connect to find the reason for rejection. Does Runway help surface rejection reasons into other tools?
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 detail about your rejection reason is 100% something that’s on our roadmap for the “App Review” step, along with making it clear who owns the task of responding to rejections if needed.
Re: Show HN: Runway – Release apps with less bouncing between Jira/GH/CI/Apple/Slack
#18YES, reduce the pain of releases for teams, all makes sense but how does this work for a one wo/man show, if at all?
Re: Show HN: Runway – Release apps with less bouncing between Jira/GH/CI/Apple/Slack
#19Would have loved this when working on our mobile release process previously, was always such a pain.
Re: Show HN: Runway – Release apps with less bouncing between Jira/GH/CI/Apple/Slack
#20YES, reduce the pain of releases for teams, all makes sense but how does this work for a one wo/man show, if at all?
We think Runway will still add value for a solo developer, but it's definitely a bit more optimized for teams at the moment.
Notably, coordinating communication and understanding the status of the work between multiple team members wouldn't come into play, but there would still be value in seeing the status of individual steps and tools consolidated together, as well as reconciling code + tickets, and understanding overall progress towards a release.
A version of Runway that is more explicitly geared towards solo developers is certainly something we've thought about and may dig into further!