What this module should change
You will be able to separate reusable task logic from a fixed screen layout and document the choices a pattern must preserve.
Module guide
Four decisions to understand
Pattern anatomy
Patterns describe a problem, entry conditions, flow, decisions, recovery, and outcomes across several components.
Rewrite a screenshot-based specification as a sequence of user intent, system response, and recovery.
Navigation
Navigation patterns preserve orientation while adapting hierarchy and input to the platform.
Identify the current location, parent, peer destinations, exit, and back behavior in one product flow.
Forms and validation
Good forms reduce questions, clarify expectations, preserve input, and place recovery guidance where it can be used.
Test a form with invalid, incomplete, slow, duplicated, and interrupted submissions.
Feedback and recovery
Feedback should answer what happened, what changed, whether work continues, and what the user can do next.
Replace one generic error with a message that names the problem, preserved work, and next action.
Working principles
Start with consequence
The severity, reversibility, and scope of an outcome determine confirmation and recovery—not the visual component alone.
Keep policy visible
Authentication, privacy, permissions, and destructive behavior are product rules that must appear in the pattern specification.
Test the whole journey
Accessible components cannot compensate for broken focus, unclear content, or lost state across a flow.
Saved in this browser
Practice and check your understanding
Explore next