Immutable User Interfaces
summary
Claims a concrete architecture: pure-function components + immutable models (Immutable.js) + network queries shaped by GraphQL fragments so each view fetches exactly what it needs. Shows how persistent data structures enable structural sharing and cheap memoization to hit 60fps, how optimistic updates and a replayable action queue handle flaky networks and concurrent edits, and demonstrates fewer round trips than REST (avoiding the 3–5s latency hit) with real libraries and examples that actually run.
AI-written summary · about
chapters (11)
- 0:00Introduction and Goal
- 1:53Architectural Principles
- 5:07Challenges in Modern Apps
- 8:43The Immutable Approach
- 11:35UI Components and Data
- 18:09GraphQL Introduction
- 23:21Structural Sharing
- 25:31Memoization Techniques
- 29:13Handling Asynchronous Actions
- 32:43Summary and Future Outlook
- 35:48Q&A Session
related talks
31mImmutable Application Architecture
34mFunctional UIs and Unidirectional Dataflow
31mImmutable Data and React
48mMutable or Immutable? Let's do both!
30mReact state management in a GraphQL era
29mWrite Queries, Not Code
34mMutable or Immutable? Why not both!
01h 02mDesigning a Flexible UI Architecture with React and GraphQL