Running An Effective Mobile Engineering Team

on YouTube ↗32m

" summary

Explains why shipping compiled apps forces different practices than web code and argues against ad hoc “YOLO” releases by showing concrete fixes: automate signing and deployment with Fastlane, distribute betas through TestFlight, adopt a release train and trunk‑based branching, and use feature flags for risky changes. Describes app store review delays and certificate friction, gives operational steps to get from weeks of bug‑fix latency to regular daily or weekly releases, and reports fewer rollbacks after automation.

AI-written summary · about

" chapters (4)

1. 0:00Welcome
2. 1:51Leading mobile teams
3. 17:12Boosting team productivity
4. 25:54Next steps

" related talks

• 22mFrom Chaos to Control: Future-Proofing Your Android Release ProcessKeegan Rush · droidCon USA 2026
• 30m10 Ways to Improve How You Ship SoftwareBrandon Bayer · Shift Miami 2023
• 40mBuilding predictable and high performance workflows for mobile app developmentRagunath Jawahar · Fragments 2019
• 11mWorking with sharp tools - A case study of Continuous deploymentHaavard Gulbrandsen · Mobile Era 2017
• 41mKeynote: Is the Developer Lifecycle Dead?Thomas Dohmke · TestMu Conference 2026
• 11mStarting Small to Growing BigNikita Leonov · AltConf 2019
• 21mManipulating organizational dynamics to improve app development processesMasato Ishigaki · iOSDC Japan 2020
• 32mHow Your Deployment Strategy Influences How People CodeChris Ng · LibertyJS 2019