Documentation
README
UI Review
Purpose
Critique an interface in a way that improves it. A critique of "it feels cluttered" is a symptom report; a critique that identifies three elements competing for the same visual weight is a fix.
When to Use
- Reviewing a mockup, a screenshot, or a live interface.
- A design that "feels wrong" and nobody can say why.
- Before a design goes to engineering.
- Auditing an interface for consistency.
Capabilities
- Hierarchy analysis: what is read first, and is it the right thing?
- Affordance: does the interface communicate what can be done?
- Consistency against a system.
- State coverage: empty, loading, error, overflow.
- Feedback that is specific enough to act on.
Inputs
This is the opening of the README. Read the full README on GitHub.