🤯 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://lunaticoin.blog","origin","homeMetadata",{"_386":1328,"_1315":1329,"_1114":1324,"_1330":57,"_1331":57,"_1332":23,"_1333":23,"_1334":1335,"_1336":1337},"Lunaticoin","ipfs://bafkreicbleoxq7kuohibnqo67ukpj6pwhnddzzzvwijztydnoaj4zzspy4","layout","seedExperimentalLogo","showOutline","showActivity","contentWidth","L","theme",{"_1338":1339},"headerLayout","Center","originHomeId",{"_569":1342,"_36":1343,"_545":1344,"_540":-5,"_571":-5,"_572":-5,"_573":-5,"_574":-5},"z6MkpHiG87oJnyMajxKyJcEwNRTbrHWjKSnmVxuuxq7bP3nb","hm://z6MkpHiG87oJnyMajxKyJcEwNRTbrHWjKSnmVxuuxq7bP3nb",[],"meta",{"_1347":1348,"_1410":1411},"values",{"_1349":1350,"_1352":1353,"_1354":1355,"_1356":1357,"_1359":1360,"_1361":1362,"_1363":1364,"_1366":1367,"_1368":1369,"_1370":1371,"_1372":1373,"_1374":1375,"_1376":1377,"_1378":1379,"_1380":1381,"_1382":1383,"_1384":1385,"_1386":1387,"_1388":1389,"_1390":1391,"_1392":1393,"_1394":1395,"_1396":1397,"_1398":1399,"_1400":1401,"_1402":1403,"_1404":1405,"_1406":1407,"_1408":1409},"document.generationInfo.generation",[1351],"bigint","dehydratedState.queries.0.state.data.document.generationInfo.generation",[1351],"dehydratedState.queries.1.state.data.document.generationInfo.generation",[1351],"dehydratedState.queries.1.queryKey.2",[1358],"undefined","dehydratedState.queries.2.state.data.0.createTime.seconds",[1351],"dehydratedState.queries.2.state.data.0.updateTime.seconds",[1351],"dehydratedState.queries.2.state.data.0.sortTime",[1365],"Date","dehydratedState.queries.2.state.data.0.activitySummary.latestCommentTime",[1358],"dehydratedState.queries.2.state.data.0.activitySummary.latestChangeTime.seconds",[1351],"dehydratedState.queries.2.state.data.0.generationInfo.generation",[1351],"dehydratedState.queries.2.state.data.0.redirectInfo",[1358],"dehydratedState.queries.2.state.data.1.createTime.seconds",[1351],"dehydratedState.queries.2.state.data.1.updateTime.seconds",[1351],"dehydratedState.queries.2.state.data.1.sortTime",[1365],"dehydratedState.queries.2.state.data.1.activitySummary.latestCommentTime",[1358],"dehydratedState.queries.2.state.data.1.activitySummary.latestChangeTime.seconds",[1351],"dehydratedState.queries.2.state.data.1.generationInfo.generation",[1351],"dehydratedState.queries.2.state.data.1.redirectInfo",[1358],"dehydratedState.queries.3.state.data.0.createTime.seconds",[1351],"dehydratedState.queries.3.state.data.0.updateTime.seconds",[1351],"dehydratedState.queries.3.state.data.0.sortTime",[1365],"dehydratedState.queries.3.state.data.0.activitySummary.latestCommentTime",[1358],"dehydratedState.queries.3.state.data.0.activitySummary.latestChangeTime.seconds",[1351],"dehydratedState.queries.3.state.data.0.generationInfo.generation",[1351],"dehydratedState.queries.3.state.data.0.redirectInfo",[1358],"dehydratedState.queries.5.state.data.document.generationInfo.generation",[1351],"dehydratedState.queries.5.queryKey.2",[1358],"dehydratedState.queries.6.state.data.metadata.icon",[1358],"dehydratedState.queries.6.state.data.metadata.summary",[1358],"referentialEqualities",{"_1349":1412,"_1354":1413,"_1361":1414,"_1370":1415,"_1376":1416,"_1390":1417},[1352],[1374],[1368],[1402],[1382],[1396],"actionData","errors"]