🤯 The UI Logic Spiral

Let’s be honest: your React component’s state logic probably started simple.

A couple of booleans. Maybe a useEffect. Just enough to get things working.

But then things changed:

You added a loading state.
Then an error state.
Then a retry flow.
Then an edge case where loading and error coexist.

Now you’re juggling isLoading, hasError, isSubmitting, showModal, and a nest of if/else blocks — and you’re still not sure you’ve covered all the cases.

Sound familiar?

🧠 UIs Aren’t Just State — They’re Behavior

We often treat UI state as a flat structure of booleans or enums.

But in reality, your UI is a process. A sequence. A user clicks a button, something happens, and the UI responds.

That’s not just state. That’s state over time — and that’s exactly what state machines are made for.

✅ The Solution: Model Behavior, Not Just State

What if, instead of wiring together a dozen flags, you modeled your UI logic as a state machine?

With a state machine, you:

Define all possible states up front
Describe only valid transitions
Eliminate contradictory or impossible states
Get a visual map of your logic — for free

Let’s look at a simple example.

🧪 Example: Toggle with XState

import { createMachine } from 'xstate';\n\nconst toggleMachine = createMachine({\n  id: 'toggle',\n  initial: 'inactive',\n  states: {\n    inactive: {\n      on: { TOGGLE: 'active' },\n    },\n    active: {\n      on: { TOGGLE: 'inactive' },\n    },\n  },\n});

That’s it.

One machine. Two states. One event. No booleans. No conditionals. No useState.

Simple, expressive, and type-safe.

🔍 Visualizing It

Here’s what that machine actually looks like:

$\"State$ State machine visualizer from stately.ai

Button

Tools like Stately.ai let you see your machines as flow diagrams — so you and your team instantly understand what’s going on.

🛠️ Why This Matters

This isn’t just for toggles. You can use state machines to:

Simplify multi-step forms and wizards
Model modals, dropdowns, or onboarding flows
Eliminate inconsistent UI states
Replace messy useEffect logic with declarative transitions

And when you pair XState + React + TypeScript, you unlock type-safe, testable UI logic that scales.

⏭️ Coming Up Next: States, Events, and Transitions

In the next issue, we’ll break down the three building blocks of any state machine — and how to spot them in your own components.

You’ll learn how to go from messy state to modeled behavior in minutes.

💡 Try This

Pick a small UI interaction in your app — a toggle, modal, or dropdown — and try modeling it as a state machine.

Just one.

Then ask yourself: was this easier to reason about?

Hit reply and let me know how it went — or tag me on Twitter/X. I’ll feature a few community examples in future issues.

Thanks for reading,\nHoracio

","enableWebSigning","https://dailyplanet.io","origin","homeMetadata",{"_393":1296,"_1283":1297,"_1298":1297,"_561":1299,"_1121":1292,"_1300":64,"_1301":1297,"_1302":1303,"_1304":8,"_1305":1306,"_1307":1308},"Daily Planet","ipfs://bafkreibwi4h3nzuc7invuqbq55pdsa4n6gyh2stz6a6a5vi2qylp62w2na","thumbnail","ipfs://bafybeifzrxuorbf6gmsw65r3ro3t5jko3vvhbuxeiljflvvysmg447di6m","layout","seedExperimentalLogo","seedExperimentalHomeOrder","CreatedFirst","showOutline","contentWidth","L","theme",{"_1309":1310},"headerLayout","Center","originHomeId",{"_576":1313,"_43":1314,"_552":1315,"_547":-5,"_578":-5,"_579":-5,"_580":-5,"_581":-5},"z6Mkp8UGrBu3RMJZkoNKTgBiRp7LTA2bZ2EUvqFokKDof8FW","hm://z6Mkp8UGrBu3RMJZkoNKTgBiRp7LTA2bZ2EUvqFokKDof8FW",[],"meta",{"_1318":1319,"_1367":1368},"values",{"_1320":1321,"_1323":1324,"_1325":1326,"_1327":1328,"_1330":1331,"_1332":1333,"_1334":1335,"_1337":1338,"_1339":1340,"_1341":1342,"_1343":1344,"_1345":1346,"_1347":1348,"_1349":1350,"_1351":1352,"_1353":1354,"_1355":1356,"_1357":1358,"_1359":1360,"_1361":1362,"_1363":1364,"_1365":1366},"document.generationInfo.generation",[1322],"bigint","dehydratedState.queries.0.state.data.document.generationInfo.generation",[1322],"dehydratedState.queries.1.state.data.document.generationInfo.generation",[1322],"dehydratedState.queries.1.queryKey.2",[1329],"undefined","dehydratedState.queries.2.state.data.0.createTime.seconds",[1322],"dehydratedState.queries.2.state.data.0.updateTime.seconds",[1322],"dehydratedState.queries.2.state.data.0.sortTime",[1336],"Date","dehydratedState.queries.2.state.data.0.activitySummary.latestCommentTime",[1329],"dehydratedState.queries.2.state.data.0.activitySummary.latestChangeTime.seconds",[1322],"dehydratedState.queries.2.state.data.0.generationInfo.generation",[1322],"dehydratedState.queries.2.state.data.0.redirectInfo",[1329],"dehydratedState.queries.3.state.data.0.createTime.seconds",[1322],"dehydratedState.queries.3.state.data.0.updateTime.seconds",[1322],"dehydratedState.queries.3.state.data.0.sortTime",[1336],"dehydratedState.queries.3.state.data.0.activitySummary.latestCommentTime",[1329],"dehydratedState.queries.3.state.data.0.activitySummary.latestChangeTime.seconds",[1322],"dehydratedState.queries.3.state.data.0.generationInfo.generation",[1322],"dehydratedState.queries.3.state.data.0.redirectInfo",[1329],"dehydratedState.queries.5.state.data.document.generationInfo.generation",[1322],"dehydratedState.queries.5.queryKey.2",[1329],"dehydratedState.queries.6.state.data.metadata.icon",[1329],"dehydratedState.queries.6.state.data.metadata.summary",[1329],"referentialEqualities",{"_1320":1369,"_1332":1370,"_1341":1371,"_1347":1372},[1323],[1339],[1359],[1353],"actionData","errors"]