Warm Up
summary
Walks through how an app moves from one-screen toy to Spotify scale, showing concrete tradeoffs: dependency injection and navigation patterns, use of mono‑repo builds (Buck/Bazel) vs CocoaPods or SPM, experiments with Combine and partial SwiftUI, and a modularization pattern using local development pods. Recommends evolving architecture rather than predicting the future, limits third‑party libraries (≈10), and migrates legacy code via incremental refactor tied to new features.
AI-written summary · about
chapters (15)
- 0:00Welcome and introduction
- 1:51Bruno’s background at Spotify
- 3:58Teaser of Bruno’s talk
- 5:41Common architecture mistakes
- 7:04Recommended architecture patterns
- 9:10Choosing package managers
- 12:18SwiftUI and widgets at Spotify
- 12:59Reactive programming with Combine
- 14:23Is SwiftUI production-ready?
- 16:07Debugging reactive code
- 18:57Remote work experience
- 21:50Conferences and community impact
- 23:15Evaluating frameworks for production
- 26:06Refactoring spaghetti code
- 27:29Closing and next week’s event
related talks
39mModularization techniques from monolithic to multi-packages app
46mPreviews and Package Oriented Programming
25mPrepping For a SwiftUI Future
01h 13mDo iOS Panel, hosted by Antoine van der Lee
21mApp architecture after introducing SwiftUI
42mThe Evolution of Presentation Patterns in SwiftUI
04mSponsors Lightning Interview #2
35mSwiftUI Performance for Demanding Apps