States: A Product Love Language
summary
Statecharts live inside modern design tools like Figma and Framer X yet rarely get shared formally; the concrete claim is to model UI components as finite state machines so engineers get exact behavior. Practical finding: statecharts are useful for compound components (media players, form widgets) but cause state explosion at app scale. Proposal: publish shared component stores with explicit state definitions to improve handoff, leverage prototypes’ declarative versus imperative modes, and stop redrawing common controls.
AI-written summary · about
chapters (15)
- 0:00Intro
- 3:18My partner, a therapist
- 5:29Declarative thinking
- 7:32Software is hard
- 9:04So we build models
- 10:19Modeling with Statecharts
- 11:28State explosion
- 13:26Transitions are Ul gold
- 14:43Where do we find components?
- 15:05Design systems!
- 15:52Design systems are structure
- 16:30Screen interaction is finite
- 17:21The common good
- 19:06Open questions
- 20:13Let's recap
related talks
27mMaking Application Logic Visually Collaborative
40mCoding Complex App Logic, Visually
39mState machines meet component libraries
07mGraphics as a Function of State/Graphic=fn(state)
24mA look into Figma product thinking
25mA Common Design Language. Let Designers and Developers talk to each other
32mA Common Design Language: Let Designers & Developers Talk to Each Other
18mMaking the Things That Help Others Do Their Thing