Frontend state management is the invisible machinery that powers how our interfaces run and feel.
Craft is not just what the user sees. Beneath the surface of most apps lies state management and architecture. It's where we spend most of our time.
1 / 5
Stop overthinking UI state
This server-rendered transcript is included so the full course content is readable by crawlers and AI systems.
Intro
The art and science of UI state
Stop overthinking UI state.
Frontend state management is the invisible machinery that powers how our interfaces run and feel.
Craft is not just what the user sees. Beneath the surface of most apps lies state management and architecture. It's where we spend most of our time.
Understand why, not just how
Understand why, not just how
It is not enough to know syntax or the techne (the know-how). You need to understand the why deeply.
The principles. The patterns. The mental models that make systems coherent.
The Problem
State management can be tricky
The act of building software should never require you to perform forensics on how and where states converge. Prop drilling, edge cases, and ill-fated attempts to synchronize state are all symptoms that something is wrong.
Yet, as systems get bigger, margins for error widen, and cracks begin to appear.
Prop drilling through layers of components
Edge cases that multiply with every feature
Ill-fated attempts to synchronize state across the app
Let's tackle this from first principles
Let's tackle this from first principles
Too often, our ideas of state can get conflated with too many other things.
Each piece of data in our app has a lifecycle spectrum that it lives across: short lived (in memory), semi-persistent (on refresh), long-lived (forever).
It emerges from many sources: user input, url, API/database.
Notice how I said data. I did not say state.
You're about to go on a journey
You're about to go on a journey
You've stumbled across this, by chance or by fate.
At each step of the way towards this new understanding, you will be equipped with maps and compasses.
Compasses - mental models to help you navigate.
Maps - production examples to debug/fix.
This won't be easy.
You will reshape and mold a new understanding of frontend architecture. The beauty, though, is that the maps are applicable forever and not tied to a framework. These are not surface-level insights.
These insights are earned through years of crafting software. This will center around 6 laws of UI State.
These are two: sync is a smell, scope determines the tool.
Early access members will receive all 6 laws with production examples. These insights alone will save you days/weeks/months of debugging pain. You'll learn not only how to architect greenfield applications, but more importantly how to refactor and fix long-standing pains.
CTA: I'm ready for the challenge.
Early access begins Spring 2026 $179 (was $250).
For more of my thoughts in the meantime, see my essay on stop overthinking UI state (link to gallery-1).