Design States, Not Screens
Feedback & States · states
Updated 2026-07-28
- Every component exists in multiple states.
- Design beyond the default:
- Loading.
- Empty.
- Error.
- Success.
- Disabled.
- Hover.
- Focus.
- Ask for every component:
- What happens before data exists?
- What happens when something fails?
- What happens after success?
- Do not leave edge cases for later.
- The quality of a product is often revealed in unusual states, not the perfect path.
- A complete component system designs the entire lifecycle, not only the first impression.
Related guides
UX Handbook