Ingredients for a healthy codebase (en)
summary
Argues that a clean architecture with a repository layer and pure-Java domain use cases makes Android apps far easier to test and maintain, replacing monolithic Activities/Fragments and singletons. Shows a working search feature wired with Retrofit, OkHttp, RxJava and Dagger 2, uses MVP presenters that emit minimal view models, and verifies behavior with unit tests plus Robolectric for fragments. Demonstrates swapping a repo for a JSON loader in tests so UI behavior stays deterministic rather than flaky.
AI-written summary · about
chapters (10)
- 0:00Start
- 8:24Clean architecture
- 12:03Data layer: repository pattern
- 14:58Domain layer
- 19:52Model vs. View model
- 22:26Presentation layer
- 24:05Communication
- 27:03Structure
- 32:28Testing
- 34:52Conclusion
related talks
31mPatterns for Safe Refactoring of Android Apps
27mHalf Way to clean architecture
40mClean, Easy & Stable Android Architecture
34mFunctional Android
22mReactive, Clean Architecture and Android Architecture Components, a solid formula for a MVVM based a
32mEffective Android Architecture
47mClean Architecture for Android
42mWorking Effectively with (Android) Legacy Code