I was wrong. I’m so sorry.

on YouTube ↗37m

" summary

Admits a prior architecture built around aggregate data sources for UICollectionView is wrong and costly: thousands of lines, fragile batch updates, and a UISplitViewController bug that leaves the master unloaded. Replaces it with an operation view controller that uses NSOperation queues (addOperation bubbled via the responder chain to AppDelegate) and a simple state machine, cutting code to a few hundred lines, improving reuse, giving a unified loading indicator, and migrating over five releases (~1.5 years) with incremental refactors.

AI-written summary · about

" chapters (10)

1. 0:00Introduction and reflection
2. 1:26Apple experience and bugs
3. 6:31Data source architecture
4. 9:26Aggregate data sources
5. 14:05App Store Connect UI
6. 17:30Architecture lessons
7. 20:07The mindset shift
8. 22:22Operation view controllers
9. 30:22Refactoring strategy
10. 33:41Conclusion and takeaways

" related talks

• 27mLow-Hanging View Controller FruitsGwen Weston · iOS Conf SG 2016
• 53mRefactor Your Way ForwardJorge D. Ortiz-Fuentes · Mobile Era 2017
• 40mMobiconf 2018: John Sundell, Swift by SundellJohn Sundell · Mobiconf 2018
• 17mApp architecture - singular vs pluralYoni Tietz · Droidcon London 2023
• 33mWarning!! New technology aheadDonny Wals · Swift Heroes 2023
• 38mArchitecture Agnostic UI DevelopmentVinay Gaba, Marcos Paulo Damasceno · droidcon SF 2019
• 38mKeynoteKrzysztof Zabłocki · Swift Heroes 2018
• 26mAdapting to change: design patterns in SwiftJesse Squires · try! Swift India 2017