Module 09 · 25 min
Hierarchy and reusable components
Hierarchy tells people what matters first. Components keep the product consistent from screen to screen.
One primary action
Each view should have one main next step. Make that button the strongest. Secondary actions stay quieter.
Reuse components
Buttons, inputs, cards, and alerts should look and behave the same across the product. That builds recognition and speeds handoff to developers.
- Same button style for the same kind of action.
- Same input pattern for forms.
- Same error pattern everywhere.