Avoid the mess! Clean up your data repository
summary
Team builds a JakeWhook app using Retrofit and Room, applies Clean Architecture with repositories and mappers, and reports the repository-as-Single Source of Truth pattern works for merging Twitter and GitHub feeds via parallel calls. Early code is messy: data models mix JSON and Room annotations, ViewModel does deletion logic, and database migrations bite. Paging integration forces workarounds—mapping in DataSource, boundary callbacks—and exposes limitations of the Paging library and Room approach.
AI-written summary · about
chapters (16)
- 0:00Start
- 6:23The Clean Architecture
- 8:43Layers
- 10:16Project Structure
- 12:57Dependency Rule
- 14:37Inversion of Control
- 15:52Data Mappers
- 19:05Data Layer
- 20:59Single Source of Truth
- 21:49How do you keep up to date
- 22:56Showcase App
- 23:29Single Remote Data Source
- 27:06Double Remote Data Source
- 29:03Paged Data Source
- 32:45Paging with Room
- 35:53Get Connected
related talks
27mHalf Way to clean architecture
42mIngredients for a healthy codebase (en)
40mClean, Easy & Stable Android Architecture
36mGet a Room
39mDatabase handling with Room
22mReactive, Clean Architecture and Android Architecture Components, a solid formula for a MVVM based a
47mArchitecting your Android app with Jetpack
28mCleaning Cleaned Clean Architecture