Flux Architecture with Xamarin
summary
Compares MVC and MVVM to a Flux-style approach implemented with Xamarin.Forms, showing stores, actions, a dispatcher (using the framework messenger) and Redux reducers for state changes. Demonstrates a profile-update flow that can sync remote and local stores and a ListView filter implemented as reducer logic. Claims unidirectional data and immutability cut side effects and unidirectional data flow complexity, reducing dozens of edge cases so viewmodel tests drop from roughly ten to about two.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:44Bug Fixing
- 1:36Obstacles
- 2:10Related Terms
- 4:00MVC
- 5:45MVC Architecture
- 10:41Problems with MVC
- 11:44Flux Architecture
- 12:51Additional Layers
- 13:51Data Store and Action
- 16:28Dispatch
- 17:54Verification
- 20:41Reducers
related talks
56mFluxing Up Your .NET Apps
46mHow I learned to stop worrying and loved the flux
36mThe Flux Pattern: MVC Framework for Data
31mFlux: Utilize unidirectional data flow ...
31mApplying Unidirectional Data Flow Beyond the ReactJS Ecosystem
19mSwiftUI Data Flow with Redux
59mReact, Flux and the Right Abstractions
13mHow we learned the hard why following a flux pattern matters