Onion-like iOS Architecture Solution
summary
Proposes a layered architecture that keeps UI controllers dumb, moves networking into a separate delivery layer, transforms responses in an independent storage layer, and holds tiny shared-state managers between them so coordinators only wire screens and data. Shows a working custom Spotify client and claims the coordinator library is under 200 LOC. Cites a real sports-betting app with 100+ UIViewController and 7–9 external services and ~15 small project objects, reporting linear maintenance costs and successful scaling.
AI-written summary · about
chapters (14)
- 0:00Introduction to speaker
- 1:14Architecture necessity
- 2:22Modern app challenges
- 5:10Case study complexity
- 8:29Layered architecture
- 12:18Solving massive view
- 15:30Coordinators and state
- 20:15Tools and demo setup
- 22:25Data delivery implementation
- 24:47Data storage layer
- 27:37Middle management layer
- 31:26Dependency injection
- 33:11UI and navigation
- 35:30Benefits and conclusion
related talks
38mKeynote
40mMobiconf 2018: John Sundell, Swift by Sundell
07mModel View Controller
33mMVVM as good (anti)pattern in iOS
21mHow not to end up your app to a hot mess of spaghetti Carbonara
45mDynamic navigation in modularised iOS apps
29mConductors: It’s all about communication!
53mRefactor Your Way Forward