Clean, Easy & Stable Android Architecture
summary
A simple Jelly Bean recipe app demonstrates a three-layer architecture (presentation/domain/data) with concrete choices: ViewModel objects hold UI state, LiveData provides lifecycle-aware observers to avoid leaks, and Room + DAOs give a compile-time-checked local SQL store. A Firebase client plus a cache and repository layer show swapping backends without changing UI code. Use-case interactors convert view models to data models and persist them; the demo app saves and restores jellybeans across rotations and works end to end.
AI-written summary · about
chapters (45)
- 0:00Intro
- 0:26Britts background
- 1:17Who is Britt
- 2:19When everything is changes
- 2:46My first startup
- 3:55William Shakespeare
- 4:58What makes sense for me
- 6:14Goals
- 8:22Architecture Components
- 9:06Personal Question
- 10:45Three Layers
- 11:38Example
- 12:06Presentation Layer
- 12:27View Model
- 13:13Set View Model
- 13:28View Model State
- 14:31Update View Model
- 15:16Live Data
- 16:24Live Data Object
- 17:06Observer
- 17:35ViewModel
- 19:54ViewModelProvider
- 20:41Multiple View Models
- 21:15Save Jelly Bean
- 21:25Data Layer
- 22:22Data Model
- 23:07Repository
- 24:02Jellybean
- 24:38Firebase
- 25:25Interactors
- 25:49Use Cases
- 26:03Business Logic
- 26:35Jelly Bean
- 27:44Layer Interaction
- 28:15Reuse Interactions
- 28:56Domain Layer
- 29:35Room
- 31:12Entity
- 31:45Dowel
- 32:00DAO
- 32:29SQL
- 32:39Database Instance
- 34:28Notifications
- 36:24Conclusion
- 36:41Questions
related talks
39mClean app design with Architecture Components
47mClean Architecture for Android
47mArchitecting your Android app with Jetpack
39mAndroid Architecture Components: fit like a glove
42mIngredients for a healthy codebase (en)
30mClean App Design with Architecture Components
47mClean app design with Architecture Components
40mI Wrote an App Using Architecture Components… And Here’s How It Turned Out