Modern RxSwift Architectures
summary
Library RxFeedback extends RxSwift with a system operator that models cyclic data flows (example: paging where “next page” URL is state) and turns effects into events that a reducer consumes. Claims: the common feedback pattern covers ~90–98% of cases, pure state + events is only ~5% of code, and it handles cancellation and reentrancy edge cases automatically. Built-in support for persisting state lets long-running work resume after restart, tests replace feedback loops with mocks, and no performance issues appear on modern devices.
AI-written summary · about
chapters (11)
- 0:00Introduction to RxFeedback
- 1:21Problems with data flow
- 3:18Modeling system state
- 6:10The RxFeedback architecture
- 7:52System operator overview
- 9:10Common feedback loop patterns
- 11:08Performance and comparisons
- 13:20Code consistency and benefits
- 15:46State management advantages
- 17:56Testability and edge cases
- 20:10Reentrancy and conclusion
related talks
34mEffective Reactive Architecture
30mReactive State Machine
24mEveryday Reactive
28mApplying Rx Best Practices to Your Architecture
21mSwiftUI & Redux
01h 00mReactive Programming, State Management, and Redux for the Modern Front End Dev
40mFunctional iOS Architecture in the SwiftUI Era
28mThe Art of Functional State Management