Atlas · DS164 · Interaction principle: Trust
Trust-Centered UI
Makes consequences, costs and system state transparent.
- Status in 2026: Active. In current use.
- Trend 2027 to 2030: Rising (an editorial projection, not a forecast).
- The term: Known technical term or standard.
Definition
Makes consequences, costs and system state transparent.
Traits
- disclosure
- logs
- provenance
Typical settings: Finance, AI, B2B.
When to use it, and when not
Consider it when the task and motivation match: people making high-impact decisions. Typical settings: finance, ai, b2b.
Be careful when the risk below would hurt the main task: sophisticated appearance masks risk.
The audience is a hypothesis
"People making high-impact decisions" describes a motivation, task or context for which this direction tends to be chosen. It was not measured, and it says nothing about any age, gender or other group.
UX risk and how to reduce it
Risk: Sophisticated appearance masks risk.
Mitigation and accessibility: Clear limit messages and auditing.
How to check: Test a prototype against a plain baseline on a real task: completion, time, errors, comprehension, accessibility and preference, segmented by context rather than by stereotype.
Evidence
Indirect: the sources support underlying principles, not a preference for this style.
The sources below support the principles that apply to this term. None of them shows that this style works better or is preferred.
- Hassenzahl 2004 (Supported): Pragmatic and hedonic qualities.
- Nielsen Norman Group 2026 (Standard or guideline): Appeal and perceived usability.
Heuristic scales
Relative editorial judgements from 1 to 5. They are not results of a study and not a measure of quality.
- Visual complexity heuristic
- 2 / 5 (1 is few visual elements, 5 is many layered elements)
- Expressiveness heuristic
- 2 / 5 (1 is restrained, neutral, 5 is highly expressive)
- Information density heuristic
- 3 / 5 (1 is sparse, 5 is dense)
In our library
No design-style recipe in @codeatlasdev/ui implements this term yet. You can still build it from the --ca-* tokens: see Theming.
Prompt for your AI
Paste this into a coding agent. It carries the trade-offs, and asks for a baseline to compare against.
Design this interface in the "Trust-Centered UI" direction (interaction principle, trust): Makes consequences, costs and system state transparent. Visual and interaction traits to use: disclosure, logs, provenance. Main UX risk: Sophisticated appearance masks risk. Mitigate it: Clear limit messages and auditing. Keep it accessible to WCAG 2.2 AA: contrast, visible focus, keyboard operation, 24 px minimum targets, reflow at 320 CSS px and reduced motion. Keep the content, hierarchy and behavior the same as a plain baseline so the two can be compared. Do not claim the style performs better; the choice should be validated with users.
References
Hassenzahl (2004). The Interplay of Beauty, Goodness, and Usability in Interactive Products. Human-Computer Interaction, 19(4).Supported
Supports: Two studies with four MP3-player skins: goodness depended on perceived usability and hedonic attributes, while beauty largely depended on identification, a hedonic attribute. Beauty and goodness were related but not the same.
Does not support: Results for other products, tasks or populations. The products were four skins of one kind of player.
Checked 2026-10-25.
Nielsen Norman Group (2026). The Aesthetic-Usability Effect. NN/g article (revised 2026).Standard or guideline
Supports: Users are more tolerant of minor usability issues in an interface they find visually appealing, and this can mask problems during usability testing; illustrated with a single test participant on one e-commerce site.
Does not support: An effect size, or that appeal improves task performance. The article's example is one participant; it is a practitioner synthesis, not a controlled study.
Checked 2026-10-25.