Boundaries in Practice
summary
Argues that “Functional Core, Imperative Shell” saves pain by moving stateful networking and routing out of view controllers: builds a StoryContainerViewController that fetches by story ID, a RemoteContentProviding protocol with Associatedtype, and a generic RemoteContentContainerViewController so StoryDetailViewController stays immutable and non-optional. Demonstrates a concrete coordinator tree (ApplicationCoordinator, tab and feature coordinators, start()) used in a side project and later integrated into Venmo, and notes avoiding storyboards to keep controllers decoupled.
AI-written summary · about
chapters (5)
related talks
18mBuckets of Code
17mMVC: Many View Controllers
43mRefactoring a Massive View Controller in Swift
40mFunctional iOS Architecture in the SwiftUI Era
22mIn defense of Core Data
28mFlexible View Controller Interfaces With Swift 4
19mThe Art of Functional State Management for iOS Apps
25mPrepping For a SwiftUI Future