Choices and navigation
Jakob's Law
Use familiar interaction patterns so people can spend their attention on the task.
The idea in plain language
What it means.
People arrive with expectations learned elsewhere. Recognizable labels, controls and navigation reduce the amount of interface behavior they need to figure out. Familiarity is a starting point for testing, and the relevant conventions depend on the audience and platform.
Evidence and interpretation
What supports it.
Jakob Nielsen's usability heuristic, presented by its author. It is not a universal experimental law or a requirement to copy another product's layout.
From principle to interface
Where you could use it.
Proposed applications, not tested outcomes. The expected effects are hypotheses to check with realistic tasks and users.
Application 1
Build account settings
Use recognizable Profile, Notifications and Security labels, with consistent Save behavior across panels.
Expected effect to test
A new user can predict where to find a setting and how a change takes effect.
Keep in view
Existing customers may have a different learned model; test migrations and explain changed behavior.
Application 2
Introduce a novel AI workflow
Keep ordinary file selection and review controls familiar while explaining the unfamiliar model action in plain language.
Expected effect to test
People can focus on what the AI will do with their input.
Keep in view
A familiar-looking button must not conceal new data sharing or an irreversible action.
Turn the idea into a check
Use it deliberately.
- Identify the products and platforms your intended users already know.
- Use familiar controls with accurate labels and consistent behavior.
- Test first-use comprehension before relying on convention.
Where the rule gets complicated
Keep the limits attached.
- A widespread pattern can still be inaccessible or confusing.
- Conventions vary across languages, cultures and devices.
- Familiarity does not authorize copying protected assets or another product's branding.
A named principle does not settle an accessibility requirement, prove a conversion lift or replace testing the particular interface.
Application and implementation boundaries
What the application check shows.
Familiar native controls behaved consistently in the local example. No first-use comprehension or cross-cultural expectation study was run.
Methods: Local application example. A completed check covers the stated sample; it is not a safety certification.
- Target
- Original IonBin synthetic interface example; no external product or human-participant study.
- Version or capture
- 2026-10-19 local fixture
- Integrity scope
- SHA-256 f85d1056afd667225a1e0364edfb8f25b4693ffa7b2b8c7d7af5b92338b85ee4 identifies the exact HTML fixture only.
Test conditions
- 155.0.8059.82 Chromium; fresh context with all network requests blocked.
- Synthetic inputs, memory-only state, reduced-motion preference, 1280px and 320px viewports.
Individual checks and observations
Native choice
passLocal application example: Exercise the original local application fixture and inspect the resulting controls or DOM state.
Observed: Keyboard ArrowDown selected PDF and the visible label matched.
Cancel is nondestructive
passLocal application example: Exercise the original local application fixture and inspect the resulting controls or DOM state.
Observed: Cancel retained the synthetic draft and returned focus to Delete.
Security findings and boundaries
Review of the local example’s stated interaction boundaries; no backend, authentication, production permissions or external service was exercised.
Practical advice · caution
Familiar appearance does not establish consent
A standard-looking button can trigger unfamiliar data sharing. Name the actual destination and consequence before a service write.
Practical caveats
- Keep Save, Share and Publish meanings distinct; validate what new users expect rather than assuming familiarity.
What remains untested
- This checks an authored application example, not the truth, effect size or generality of the named principle.
- No users, assistive-technology participants, physical devices or production task outcomes were evaluated.
Security limits
- The example has no real authorization or persistence layer; its UI behavior cannot establish the security of a deployed workflow.
Evaluation sources
- Jakob Nielsen: Jakob's Law of Internet User Experience
Author's statement of the heuristic.
Go to the source
Research and further reading.
- Jakob Nielsen: Jakob's Law of Internet User Experience
Author's statement of the heuristic.
Related questions
More on choices and navigation.
Research finding
Hick's Law
Make the next decision understandable. Removing useful choices is only one possible way to do that.