Building Event Driven User Interfaces
summary
Argues that moving from shared Redux-style stores to local mutable state coordinated by a message bus reduces coupling and brittle tests, with concrete C#/Blazor Web Application examples. Shows an edit reservation page implemented as a local state machine that publishes request events, a background service fetches data and publishes success or failure, and the component transitions and re-renders. Demonstrates fewer impure components, easier unit testing of pure UI parts, and a small Dispatcher cookbook for the message bus that proved workable.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 3:38Pure functions in UI
- 8:54Traditional state management
- 14:14Microservices challenges
- 16:41Event-driven backend
- 19:10Fractal programming
- 21:00Event-driven UI design
- 23:50Core components
- 26:23Simple event publishing and subscription patterns
- 28:09Data fetching in events
- 32:25State machines
- 36:40State machines in components
- 41:11Rendering state transitions
- 44:23Q&A
related talks
01h 03mState management in Blazor
49mArchitecting Blazor applications – An Angular inspired approach
34mFunctional UIs and Unidirectional Dataflow
28mOperate Heavily Dynamic UI’s with Rxjs
30mManaging State Management
22mComponents are the New Thin Clients
25mEnemy of the State
49mDeveloping a clean architecture-inspired React application with MVVM