Cut costs, not corners - Master modularization with SPM
summary
They refactor a monolithic iOS app to modular SPM packages (core, coreUI, feature modules), keep feature work flowing, and pull Kotlin Multiplatform into its own repo then import it as an SPM/XCFramework. Practical steps: define feature boundaries, extract shared code to core modules, avoid horizontal and downstream dependencies, and expect a huge PR and many fix-compile cycles. Measured wins are concrete: 55% local clean build time, 43% local incremental build time, 73% CI/CD build time and iOS CI drops to about 8 minutes.
AI-written summary · about
chapters (5)
- 0:00Origins of Project X
- 4:56Navigating the modularization
- 22:22Modularization results and pros
- 24:57Metamorphosis of the codebase
- 27:44The legacy and key takeaways
related talks
37mCut costs, not corners: Master modularization with SPM
42mSplitting Monolithic Swift Code Base Into Modules
01h 00mHow to Build Modularity with SPM and a Monorepo Without Going Gray
39mModularization techniques from monolithic to multi-packages app
30mA Micro-services perspective on iOS architecture
29mWarm Up
32mSpeeding up the build process of a monolithic application
51mMultimodule Project Architecture