Reactive, Clean Architecture and Android Architecture Components, a solid formula for a MVVM based a
summary
Asserts a practical recipe: combine RxJava + Retrofit with a custom reactive store behavior streams (infinite, emits current state wrapped in Option), a Clean Architecture split (data/domain/presentation), and LiveData and ViewModel to get a testable MVVM flow. Example: an N26 credits list where repository exposes get() as an infinite observable and fetch() as a Completable, the interactor triggers fetch on empty, propagates errors, maps raw→safe entities, ViewModel subscribes and posts formatted view entities to LiveData, and onClear disposes subscriptions.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:29Reactive systems explained
- 2:32Clean architecture overview
- 3:56Data layer setup
- 7:07Reactive store implementation
- 8:53Repository integration
- 10:15Domain layer interactors
- 14:07Presentation layer design
- 17:39ViewModel binding
- 19:23Fragment integration
- 20:08Architecture summary
- 21:36Resources and Q&A
related talks
42mHands on MvRx: Building Real Apps
30mClean App Design with Architecture Components
19mBuilding Reactive Views With the Architecture Components
41mMVI: a Robust and Modern Architecture
34mFunctional Android
01h 07mA Modern Approach to Android App Architecture
47mAndroid Architecture Component
40mI Wrote an App Using Architecture Components… And Here’s How It Turned Out