Applying Rx Best Practices to Your Architecture
summary
Refactors a buggy profile flow into a single event→presenter→viewmodel pipeline using RxJava primitives so side effects live only at edges and business logic stays pure. Uses PublishSubject for view events, an ObservableTransformer (presenter) that flatMaps and uses scan to build immutable view models, and replay(1).autoConnect() so views can rebind after rotation. Result: removes repeated network/profile churn, enables instant optimistic updates, and makes the code much easier to test and review.
AI-written summary · about
chapters (7)
- 0:00Introduction to Rx best practices
- 1:04Side effects in legacy code
- 6:30Refactoring with Rx streams
- 12:18Architecting with decoupled streams
- 18:23Handling configuration changes
- 21:40Adding new features cleanly
- 24:06Q&A session
related talks
34mEffective Reactive Architecture
51mManaging State with RxJava
37mA Practical Guide To master Rx Streams
42mHands on MvRx: Building Real Apps
30mArchitecting an app with MVP and ViewModels
39mAdvanced Networking with RxJava + Retrofit
49mFunctional Reactive Programming with RxJava
09mA taste of MVVM + RxSwift