Going Reactive, An Android Architectural Journey
summary
Practical case study of migrating an Android app to reactive patterns using RxJava and a tiny bit of RxAndroid, showing a reusable switchOnNext pager for endless lists, a 50-line fragment + 200-line presenter split, and an event bus built on Rx subjects for cross-feature updates. Covers a SQLite wrapper Propeller, a lifecycle binder LightCycle, a bytecode logger Gandalf, and a hard lesson about internal buffer 16 causing missing backpressure crashes.
AI-written summary · about
chapters (19)
- 0:00Start
- 6:55The Sound Stream
- 8:48Layer Objects
- 13:49Light Cycle
- 15:49Presenters
- 18:47Paging
- 21:03Use Cases
- 23:05Feature Data
- 25:28Cross-Screen Messaging
- 28:34Screen-to-Screen Updates
- 31:43Life-Cycle Subscriptions
- 32:38Fast Path & Lazy Updates
- 34:07Observable Transformers
- 35:07Deferred Execution
- 37:35ObserveOn: onError
- 38:31ObserveOn: Backpressure
- 41:48Debugging Observables
- 43:07Gandalf
- 44:45Stay in touch @mttkay
related talks
39mReactive Android: RxJava and beyond
23mWhy Reactive Programming?
22mReactive, Clean Architecture and Android Architecture Components, a solid formula for a MVVM based a
27mHalf Way to clean architecture
46mMvRx: Android Development on Autopilot
34mFunctional Android
01h 07mA Modern Approach to Android App Architecture
46mA Reactive Bicycle for the SDK