Starting Module Separation from New Feature Development
summary
The talk explains adopting a multi-module architecture for an iOS app by extracting newly developed features as separate modules. It names benefits—shorter incremental builds and looser coupling—and describes a practical approach to start modularization without halting ongoing feature development or doing large-scale refactors.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:04What we'll talk about today
- 2:54Multi-module
- 5:04Module separation from new feature development
- 6:54Defining responsibilities
- 8:49Tips: Using libraries on the framework side
- 11:37Identifying parts that should be generalized
- 12:37Breaking free from existing code
- 13:21Reducing the scope of impact
- 14:20Project file conflicts
- 17:29Future prospects
related talks
45mWhy and How to Split an iOS App into Microfeatures
39mModularization techniques from monolithic to multi-packages app
42mSplitting Monolithic Swift Code Base Into Modules
40mModularizing Android Applications
32mBuild a modular Android app architecture
20mBreaking Down Modularization
37mGrowing a Joyful Codebase from Legacy Code
34mModular Flutter App Architecture Answering the What, When and How