Name every state
Loading, empty, stale, denied, failed, completed, and recovery states belong in the interface contract before polish begins.
Interface behavior patterns
Small interfaces should make every important state obvious.
SmolUI turns one interaction at a time into a state map, annotated pattern, and acceptance check that a builder or reviewer can use before choosing a framework.
Make consequences visible
Labels, confirmation, reversal, and escalation should match what an action changes and who will feel the result.
Review without a framework
Each pattern ends with technology-neutral acceptance checks for content, focus, status communication, and backend boundaries.
Publishing next
The first reporting tracks
- A state inventory for small operational forms
- When a destructive action needs confirmation or undo
- How to review empty and failed states before implementation
- A technology-neutral interface acceptance sheet
About this publication
A small UI still carries real operational consequences.
SmolUI publishes compact interface specifications for builders and reviewers. It focuses on visible behavior and acceptance criteria, not component-library promotion, frontend authorization claims, or generic visual inspiration.