Scaling Up With SwiftUI: Migrating iOS Apps To SwiftUI
summary
Turo moves from mixed ObjC/Storyboard/UIKit to SwiftUI as the default in under nine months, using a 20‑person pod model that converts a shortlist of 20 screens to test architectures. The team standardizes on MVVM, builds a SwiftUI design system, open‑sources a storyboard-to-SwiftUI converter, splits the monolith with local CocoaPods and cocoapods-generate, adds pre-commit hooks and linters, runs workshops, office hours and code review sessions, and ships faster with better snapshot/unit tests and built‑in accessibility.
AI-written summary · about
chapters (11)
- 0:00Introduction to Turo
- 2:41Defining the transition goals
- 3:55Team education and training
- 5:22Exploring architectures
- 6:59Evaluating architectural choices
- 11:39Onboarding and style guides
- 15:06Enhancing developer tooling
- 21:33Implementing navigation
- 29:42Driving adoption and success
- 34:38Alignment with management
- 37:20Lessons learned and conclusion
related talks
37mAdopting SwiftUI at scale
41mWhen You Can’t Go All In On SwiftUI, Build a Hybrid UI App Instead!
28mElevating your design with SwiftUI
40mFunctional iOS Architecture in the SwiftUI Era
27mCode organization strategies for complex globalization in Swift
42mSplitting Monolithic Swift Code Base Into Modules
20mTools for SwiftUI adoption at scale
34mBuilding Shared UIs Across Platforms With Compose