Splitting Monolithic Swift Code Base Into Modules
summary
Ten iOS engineers split a two‑year monolith into separate Xcode projects and workspaces, moving new features into product modules and core utilities into libraries like VP Commons and VP Network. Build iteration for a module drops to seconds (main workspace clean builds near 20s), CI clean builds remain costly but targeted compiler tweaks help, a networking module hits 90% coverage, Core Data is phased out, demo apps speed UI iteration, and developer velocity and morale measurably improve under MVVM+C and TDD practices.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:00About VPTech
- 5:00The Problem
- 8:59The Mess
- 14:40VP Commons
- 18:14User Engagement
- 26:43Workspaces
- 28:38Repository
- 29:59Summary
- 33:25Questions
related talks
38m@deprecated Monolith @available Modules
32mCut costs, not corners - Master modularization with SPM
37mCut costs, not corners: Master modularization with SPM
32mSpeeding up the build process of a monolithic application
33mScaling Swift Development
41mTwo Birds with One Stone: Multimodule Architecture and Faster Builds
20mStarting Module Separation from New Feature Development
39mModularization techniques from monolithic to multi-packages app