Vuex? No, it’s X(state)Vue for UI
summary
Claims that replacing ad hoc boolean flags with explicit finite state machines eliminates common bugs and scales better, demonstrating concrete examples: a fetch flow and a toggle component implemented with XState and the xstate-vue/Composition API integration. Shows moving UI logic into machine context and actions, sharing a started service across components, using the XState visualizer to inspect transitions, and how state-driven code reduces tests to concise state/transition specs while removing fragile conditional plumbing.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:16View Tree Composition
- 7:07Finite State Machines
- 7:47Deterministic Finite Automaton
- 8:22Deterministic Final Automation
- 9:13State Machines
- 15:27Toggle Component
- 27:02X-State Visualizer
- 29:54Resources
related talks
33mVuex? No, it’s X(state)Vue for UI
40mVisualize your State Management with XState
44mScaling State in Vue: Why XState Matters
31mXState: the Visual Future of State Management
27mXState: the Visual Future of State Management
48mVueX: Vue.js applications at scale
45mState of the Art User Interfaces with State Machines
30mA UI in All Its States with XState