Runway
Day 18 after signup
The Flight Deck #36 - The Mobile Release Management Newsletter
Why Shopify dropped React Native, how to streamline your iOS release process, and the new mobile bottleneck: shipping AI written code.
Why it works
- A playful seasonal opening gives the issue personality before moving into practical engineering topics.
- Grouping outside articles, research, and Runway’s own content makes a broad roundup easy to scan while giving each item a clear purpose.
How it is built
- Seasonal opening
- Newsletter introduction
- Curated article roundup
- Research guide promotion
Email copy
View in browser Hi [First name], The witching hour is nigh, the jack-o’-lanterns are grinning, and somewhere deep in the bowels of production, a bug you fixed six months ago has risen from the dead. October is upon us again, which means it's time to write a spooky opening for the Flight Deck. We've raided the mobile engineering crypts and summoned the release management warlocks to stitch together a monstrous collection of dispatches from the other side (of your screen). Draw the curtains, light a black candle, and keep a wooden stake close at hand to quickly jam into the rollback button, as the shroud between a healthy and busted deployment is thin, and something wicked this way ships. Come along with us in this 36(66)th edition of the Flight Deck as we look at a time when a feature flag took down a critical feature in one team’s Android app, dig into how to make Xcode and agents share incremental builds, and give you a tour of our brand-new feature: Triage by Runway. Don’t worry, despite our opening paragraph, this newsletter is not haunted. Posts we liked Why has Shopify dropped React Native? Six years ago, Shopify went all in on React Native and declared it the future of mobile development. One year ago, they said its “future was bright, and they planned to keep investing in it.” Last month, they said to forget all that because Actually Native is now the future and the best way to build mobile apps. Why did they change their minds? Gergely Orosz looks at why: the cost of maintaining two codebases is no longer higher than the performance gains from going native (it’s because of AI, obviously). Prepare and submit your apps for iPhone Duo Starting in April of next year, every iOS app submitted will need to include screenshots for iPhone Duo, or it’ll be rejected. Which also means every iOS app will need to be designed for use on iPhone Duo, or it’ll be rejected. Apple has published three steps to “make your app shine” on Duo. What are those steps? They wrote an entire article about them (among many other helpful Duo focused articles) that you can find at the link above to ensure your app is prepared for our foldable future. How a forgotten feature flag took down a critical feature in an Android app A fun thing you can do with feature flags is forget about them at a crucial moment. Perhaps you launched a new version of your live chat behind a feature flag and deprecated an API that the old version of the chat depended on, but then didn’t enable the feature flag in production, so that no one had access to the new chat and everyone was stuck on the old chat which simply broke since it no longer had access to the API it needed. That’s exactly what happened to Nav Singh. Learn how this happened, how his team discovered the problem, and how they fixed it. Well, you already know how they fixed it, but you can learn the rest in his in-depth retrospective. Making Xcode and agents share incremental builds Serg Dort was getting tired of watching code build in his AI agent, then switching to Xcode to check it, only to watch it build again. It wasn’t the worst thing in the world, but the more he did it, the more annoying it became: he had to wait 20 seconds, 60 seconds, 100 seconds for an already built build to build again. Learn how he fixed this by sharing build locations and cache (along with a couple of other things). The code nobody reads In the past month, there’s a good chance you gave an agent the OK on code you didn’t fully read or even understand, and that your PR reviewers didn’t fully read or even understand either. This probably turned out okay. Maybe there was a bug, but aren’t there always? In an era of software development where velocity is everything, Addy Osmani considers what should replace reading every line of code, because something does need to replace it, it can’t just be nothing. Go figure How does company leadership perceive mobile engineering in 2026? 51% of mobile EMs say non-mobile leadership