Design Principles
Overview
Design principles connect user needs, product goals, and implementation choices.
Why It Matters
Design principles help avoid interfaces that are technically correct but hard to use.
Core Concepts
- Clarity beats density.
- Feedback should be immediate and understandable.
- The UI should communicate state, not hide it.
Mental Models
Treat every interaction as a contract: the user acts, the system responds, and the response should feel obvious.
Best Practices
- Keep primary actions obvious.
- Design for error recovery.
- Use spacing, hierarchy, and contrast intentionally.
Common Mistakes
- Hiding important actions.
- Making the user guess what happened.
- Overloading screens with equal-weight content.
Trade-offs
Minimal interfaces reduce clutter, but over-minimal designs can hide important affordances.
Decision Framework
flowchart TD
A[Design choice] --> B{Does it reduce user uncertainty?}
B -->|Yes| C[Keep or strengthen it]
B -->|No| D{Is it necessary for completion?}
D -->|Yes| E[Make it explicit]
D -->|No| F[Remove it]Examples
- Show a loading skeleton when data is pending.
- Place destructive actions behind a deliberate affordance.
Checklists
- Is the primary action obvious?
- Does the screen explain its own state?
- Can the user safely recover from mistakes?
Senior Engineer Notes
Senior engineers connect design quality to system quality. A clear interface is not decoration; it is part of the product contract.