Clean Architecture for Android
summary
A concrete Clean Architecture applied to Android at JobandTalent: app code is split into UI, presenters, interactors (use cases), repositories and three data sources (API, local, cache). Presenters stay pure Java and survive rotations via retained-fragment presenters; dependencies are injected with Dagger; background work is handled by interactors using an executor plus main-thread handler (some interactors run on the foreground); domain models are used to avoid DTO duplication, improving modularity, testability and production readiness.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 10:58Gran Pozo Activity problem
- 13:28View and logic separation
- 21:53Business logic and use cases
- 27:12Repositories and data sources
- 32:27Modular architecture and dependency rules
- 37:26Architecture benefits
- 40:34Final tips and conclusions
- 43:01Q&A
related talks
28mCleaning Cleaned Clean Architecture
39mClean app design with Architecture Components
40mClean, Easy & Stable Android Architecture
30mClean App Design with Architecture Components
27mHalf Way to clean architecture
32mEffective Android Architecture
40mOur way to the clean architecture
42mIngredients for a healthy codebase (en)