Skip to content
On this page Definition

Atlas · DS194 · Interaction principle: Emotion

Emotion-Driven UI

Color, shape, motion and language aimed at a desired affective state.

  • Status in 2026: Active. In current use.
  • Trend 2027 to 2030: Rising in some contexts (an editorial projection, not a forecast).
  • The term: Known technical term or standard.

Definition

Color, shape, motion and language aimed at a desired affective state.

Traits

  • expressive shape
  • tones
  • motion

Typical settings: Brand, Wellness.

When to use it, and when not

Consider it when the task and motivation match: people in identity-driven experiences. Typical settings: brand, wellness.

Be careful when the risk below would hurt the main task: inferring emotion without consent or basis.

UX risk and how to reduce it

Risk: Inferring emotion without consent or basis.

Mitigation and accessibility: Validate interpretation with users.

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.

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
3 / 5 (1 is few visual elements, 5 is many layered elements)
Expressiveness heuristic
4 / 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 "Emotion-Driven UI" direction (interaction principle, emotion): Color, shape, motion and language aimed at a desired affective state.
Visual and interaction traits to use: expressive shape, tones, motion.
Main UX risk: Inferring emotion without consent or basis. Mitigate it: Validate interpretation with users.
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

  1. 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.

  2. Google Design (2025). Expressive Design: Google's UX Research. design.google.Preliminary

    Supports: The vendor reports 46 research studies and more than 18,000 participants behind Material 3 Expressive.

    Does not support: Independent replication. The studies are the vendor's, the data are not published on this page, and the result concerns their own design system.

    Checked 2026-10-25.