Exploring State Management in Phoenix LiveView
summary
Demonstrates state fragmentation in Phoenix LiveView with a small lunch app, function components, stateful live components and nested live views that crash independently but don’t auto-sync, then shows a proof‑of‑concept centralized store inspired by Zustand and a persistence library LiveStash that snapshots assigns and restores them on reconnect using either an ETS adapter or a browser memory adapter with configurable TTL, and reports that the store prototype works but is not yet production ready.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:49What is state
- 4:40State management tools
- 9:54State fragmentation
- 12:20LiveState concept
- 14:09State loss on reconnects
- 16:54LiveStash recovery
- 19:46LiveState vs alternatives
- 20:50Q&A
related talks
35mKeynote: Fireside Chat on LiveView, (...)
01h 13mKeynote: Phoenix LiveView - Interactive Apps without Javascript
46mThe joy of building your startup with Phoenix LiveView
52mState management beyond the libraries
34mIntroducing LiveData: LiveView for JSON endpoints
30mTales of Using Phoenix LiveView at an Early Stage Startup
28mLobbying with Elixir: Real-Time LiveView and OTP
40mVisualize your State Management with XState