# Spring-Based Motion

DS183. Interaction pattern: Motion. Page: https://ui.codeatlas.com.br/atlas/spring-based-motion/. Index: https://ui.codeatlas.com.br/llms/atlas.txt

Motion simulated by springs for naturalness and continuity.

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

## Traits

- overshoot
- spring

Typical settings: Mobile, Editors.

## When to use it, and when not

Consider it when the task and motivation match: people using tactile and creative apps. Typical settings: mobile, editors.

Be careful when the risk below would hurt the main task: overshoot distracts in dense content.

Audience (a hypothesis about motivation and task, never measured, not a statement about any group): People using tactile and creative apps.

## UX risk and how to reduce it

- Risk: Overshoot distracts in dense content.
- Mitigation and accessibility: Tune damping and reduced motion.
- 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 support the principles that apply to this term. None shows that this style works better or is preferred.

- [E09] W3C Web Accessibility Initiative (2023). Understanding Success Criterion 2.3.3: Animation from Interactions. https://www.w3.org/WAI/WCAG22/Understanding/animation-from-interactions (Standard or guideline). Does not support: A prevalence figure, or that all animation is harmful. Essential motion is excepted, and the criterion is above the AA level most programs target.
- [E04] Hassenzahl (2004). The Interplay of Beauty, Goodness, and Usability in Interactive Products. https://doi.org/10.1207/s15327051hci1904_2 (Supported). Does not support: Results for other products, tasks or populations. The products were four skins of one kind of player.

## Limits

- The atlas is a broad, living catalogue, not every style that exists. No authority enumerates them, and the classes (movement, aesthetic, design system, layout, pattern, principle) overlap.
- The 1 to 5 scores are relative editorial judgements. They are not results of a study and not a measure of quality.
- An audience is a hypothesis about motivation, task and context. It was never measured and says nothing about any age, gender or other group.
- The sources support underlying principles (visual complexity, legibility, grouping, accessibility, platform conventions). None shows that a particular style works better or is preferred.
- The 2027 to 2030 trend is an editorial projection, not a forecast.
- Terms in the Future / AI category rest on exploratory work, some of it preprints, with no causal validation.

Last reviewed 2026-10-25.

## Heuristic scales

Relative editorial judgements from 1 to 5, not results of a study.

- Visual complexity: 3 / 5 (heuristic)
- Expressiveness: 4 / 5 (heuristic)
- Information density: 3 / 5 (heuristic)

## In our library

No design-style recipe implements this term yet; build it from `--ca-*` tokens.

## Prompt for your AI

```text
Design this interface in the "Spring-Based Motion" direction (interaction pattern, motion): Motion simulated by springs for naturalness and continuity.
Visual and interaction traits to use: overshoot, spring.
Main UX risk: Overshoot distracts in dense content. Mitigate it: Tune damping and reduced motion.
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.
```