Pragmatic crafting
summary
A four‑person team modularizes Plaid, splitting Designer News, Dribbble and Product Hunt into separate modules and shipping some pieces with dynamic feature modules so noncore flows can be downloaded or removed. The code moves to layered libraries (UI, domain, data), uses suspend functions with Room and coroutines, and reduces rebuild time to module scope. Ownership of features speeds merges, a shared pull request template improves reviews, and the refactor proves deployable with parallelized network loads and tighter encapsulation.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:42Static analysis issues Number of bugs
- 8:21Modularization
- 13:28Single responsibility principle
- 16:40Understand where you are and where you want to go
- 24:55API Usability Principles
- 25:44Empathy Communication
- 28:41Asking and receiving feedback
- 31:53Giving feedback
related talks
21m[Eng Sub]if (extensible design) return "work life balance"
39mRefactoring Plaid App – A reactive MVP approach
33mTools of the Trade
32mBuild a modular Android app architecture
49mScalable Best Practices for Your Development Team
35mShaping your app’s architecture with Kotlin and Architecture Components
32mCut costs, not corners - Master modularization with SPM
39mForging the path from monolith to multi-module app