Architecting your Android app with Jetpack
summary
An Android books app architecture built entirely with Jetpack components: Navigation XML and NavHost for navigation flows; ViewModel and LiveData for screen state; two-way DataBinding for forms; Room for local persistence with separate entity/domain/presentation Book classes and explicit mappers; WorkManager for background sync; and Paging for lists. Implementation shows problems when LiveData is pushed into repository/domain layers—causing cascading updates and a broken save-with-image flow—so LiveData should be kept at the presentation layer.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:04Android architecture principles
- 3:14MVP and MVVM patterns
- 5:44Clean Architecture layers
- 7:31Jetpack overview
- 9:21Jetpack architecture components
- 11:06Navigation Component
- 15:45Presentation layer
- 19:17Data Binding and LiveData
- 21:43ViewModel and lifecycle
- 23:50LiveData in domain layer
- 27:23Transformations and mappings
- 29:48Show/hide UI elements
- 30:10Lifecycle and LiveData
- 32:59Domain layer and use cases
- 35:27Data layer and reactivity
- 37:34Room and local persistence
- 40:45WorkManager for tasks
- 43:12Paging for pagination
- 45:21Summary and recommendations
- 46:45Conclusion
related talks
38mAndroid Architecture Components
01h 13mAccelerating Android Development with Google Jetpack
39mClean app design with Architecture Components
34mAndroid Jetpack: What's new in Architecture Components
47mClean app design with Architecture Components
40mClean, Easy & Stable Android Architecture
20mArchitecture Components
19mFirebase & Jetpack: Fits like a Glove
