Runway (runway.team) ads

Your mobile team merges more AI-written PRs than reviewers can read closely. Where do regressions get caught now? Code review used to be where you caught them. Now there's more code than reviewers can keep up with, so problems surface later: in QA, in beta, or in production. Mobile engineering leaders share which checks they moved, added or automated as AI volume grew. Live Nov 12, 10am PT / 1pm ET.

AI code volume is up. Code review capacity isn't. Mobile teams are merging more changes per release than they can fully read, and the release process was built for the old pace. Mobile engineering leaders share how they keep app releases stable anyway: what they automated, and where humans still sign off. Live Nov 12, 10am PT / 1pm ET.

Same mobile release train, same quality gates, far more AI code. Something has to give, and it's usually the release. In this live panel, mobile engineering leaders get specific: what strained first, what they automated, and where they still keep a human in the loop. Live Nov 12, 10am PT / 1pm ET

You're not a slow team. You're a fast team with a slow mobile release. AI-written PRs pile up waiting for code review, and merged work waits for the next release train. The release itself becomes the slowest step in the pipeline. Mobile engineering leaders share what they changed to keep up. Live Nov 12, 10am PT / 1pm ET.

94% of mobile EMs spend three or more hours a cycle just telling people what the status of the release is. The 2026 Decision Guide shows how teams get those hours back.

Introducing Triage by Runway. Mobile teams have a lot that lands on their plates: regressions flagged by QA, feedback from beta testers, user reviews in the app stores, new crashes, unhealthy metrics, and much more. And this influx is growing: with AI, the volume and velocity of changes is skyrocketing, so there are more issues flowing in and it’s that much harder to handle them efficiently and appropriately. It’s easy to lose track of important items and difficult to identify trends, prioritize properly, assign to the right owners, and actually get fixes in. Dealing with this firehose of issues is a big time sink and things often slip through the cracks. We built Triage as the solution: a consistent, centralized, and automated inbox to consolidate all issues from all sources, help teams take action on those, and reduce busywork and risk throughout. With Triage, your team gets: - A unified view that consolidates issues with full context on source and status - Automatic assignment based on signals like code authorship, linked tickets, and historical patterns - Detection of duplicate and related issues, with automatic reconciliation - A direct path from issue to fix request without leaving Runway, plus auto-created tickets in your project management tool and updates via Slack, Teams, or email - MCP coverage, so agents can pick up open issues or surface new issues of their own Watch highlights 👇 below, or head to our sandbox to see Triage in action: https://lnkd.in/gRdVWfkr/?utm_campaign=JDM_AllGeos_TOF%252BMOF_Thought-Leadership_Engagement&utm_source=linkedin&utm_medium=paid&utm_id=671184344&hsa_acc=507170233&hsa_cam=671184344&hsa_grp=490615164&hsa_ad=1550835484&hsa_net=linkedin&hsa_ver=3