Exploring the States of UI Design

The Daily Interesting — Art & Design Edition

March 27, 2026

The idea

“UI is a function of state” is a pretty popular saying in the front-end world. In context (pun intended), that's typically referring to application or component state. I thought I’d pull that thread a little further and explore all the states that can effect the UI layer.[1][2]

Nothing • Loading • None • One • Some • Too Many • Incorrect • Correct • Done[1][2]

— Vince Speelman (BarnsworthBurning extract)[1]

Who said it (and the context)

Vince Speelman is a designer, front-end developer, and speaker—once at TED.com—who shares pragmatic takes on crafting resilient interfaces. This 2015 essay arose from modern UI teams' focus on components over pages, urging attention to the "unhappy path" where users veer off ideal flows, like empty lists or errors.[2][3]

A small expansion

Speelman's nine states map a component's full lifecycle—from inert "Nothing" to overflowing "Too Many"—reminding designers that polished "Some" (the happy norm) ignores real-world flux, like loading waits or input errors. Designing them proactively builds empathy and elevates experiences.[2]

Another lens on the idea

Dave Rupert builds on it with "UI = f(statesⁿ)," stressing combinations of states (e.g., loading + error) explode possibilities, pushing systematic planning for robust, empathetic design over siloed happy paths.[4]


Why this matters across art and design

  • Visual identity
    Brand elements shift states too: "None" (unloaded logo), "Incorrect" (distorted resize), "Too Many" (cluttered variants)—audit for coherence across contexts.[1]

  • Product & UX
    Core fit: lists go "Empty/None" to "Paginate Too Many"; forms hit "Incorrect/Correct"—pre-design these to guide users smoothly.[2]

  • Architecture
    Spaces evolve: "Loading" (under construction scaffolding), "None" (echoey vacancy), "Too Many" (overcrowded)—layer states for adaptability.[1]

  • Studio art
    Canvas states: "Nothing" (blank), "Loading" (wet paint drying), "Incorrect" (failed layer)—embrace them as iterative phases in process art.[2]


Two quick drills

  1. State Spectrum Scan (10 minutes)
    Pick a component/sketch. Map all nine states—what shows now? Gap-fill one "unhappy" (e.g., "Too Many" pagination).[2]

  2. Unhappy Path Prototype (15 minutes)
    Wireframe three combos (e.g., Loading + Error). Test mentally: Does it reassure or frustrate?[4]


Thread to remember

Links modular components (45), hands-on refinement (46), and squiggle mess (38)—states expose failure forms (18) for iterative craft, like verb actions (3) across scales (32).


Sources

Try this today: Scan your latest design—which state lurks forgotten?