Motion tokens

Preview

Installation

npm install echo-ui-core

At a glance

Weight

433 B (minified and gzipped; React not counted)

Needs

gsap

Reduced motion

Each token declares its own collapse: summon, flood, bloom and island fade in place, boot fades quickly; every other token stops moving. Springs are skipped: the part jumps to where it is going.

Usage

import gsap from "gsap";
import { motion } from "echo-ui-core/motion";

const t = motion.summon;
gsap.to(panel, { opacity: 1, duration: t.duration / 1000, ease: t.ease });

Examples

const t = motion.summon;
gsap.to(el, { opacity: 1, duration: t.duration / 1000, ease: t.ease });

const { ref, handlers } = useTactile({ press: { motion: "press" }, release: { motion: "pop" } });

const t = motion.summon;
const vars = reduced && t.reduced !== "none" ? { opacity: 1 } : { opacity: 1, scale: 1 };

Motion & sound

Motion tokens

press, pop, summon, breath, settle, glitch, flood, drain, lift, follow, travel, squash, rebound, light, boot, bloom, island

Reduced motion

Each token declares its own collapse: summon, flood, bloom and island fade in place, boot fades quickly; every other token stops moving. Springs are skipped: the part jumps to where it is going.

Props

Anti-patterns

• Never put a soft material ease on a pixel element — an LCD or dot-matrix surface takes glitch (steps), never summon or settle. This is the single most legible motion mistake in the system.
• Never invent a duration inline. If a gesture needs timing the tokens do not cover, add a token and document it; scattered magic numbers are how a motion system dies.
• Never animate a token's transform under prefers-reduced-motion — read reduced and collapse to the fade (or to nothing) as the token instructs.
• Never use drain with a duration — it is scrub-driven, timed by the clock that owns it, which is why it ships no duration at all.

Changelog

• v0.3.0 · 2026-10-12 · ChangedEvery item needs echo-ui-core 0.3.0 (all components). The drawn device, readability past AA and the design tests live in core, and the components that use them are built against it, so each item now declares echo-ui-core >=0.3.0 <0.4.0. Update core with the items: npm install echo-ui-core@^0.3.0 (or your package manager's), then npx echo-ui-cli update. An item whose files didn't change is the same code under a new version; the 0.2.0 files stay published.
• v0.2.0 · 2026-10-04 · ChangedComments only, no behaviour change. Comments in the component source used to cite documents, milestones and ticket numbers from Echo's own planning, none of which exist in your project. The citations are gone and the sentences around them stay. Where a comment was only a citation, it now says what it meant. Three development warnings (HardwareButton's engraved/caption checks and StatusDot's missing-label check) also dropped the ticket code at the end of the message. echo-ui diff will show changes in most items; none of them are to code.
• v0.2.0 · 2026-10-04 · ChangedAn item's version is now a function of declared data, not of how the changelog is formatted. The version an item ships under is published once and never rewritten, and it used to be inferred from prose: a regex for a bolded "Breaking" run across the whole unreleased section, and attribution by "does a bullet mention this name in backticks". One breaking entry therefore moved every item that changed that cycle, and an entry explaining that "Menu and Sheet are unchanged here" filed itself as a change to Menu and Sheet — which it really had.
• v0.2.0 · 2026-10-04 · ChangedThe agent brief says Echo has not shipped. llms.txt and the MCP server's instructions led with npx echo-ui-cli init, and that name on npm is a reserved stub with no executable — so a model following the brief wrote an install step that fails with npx's own error. The brief now opens with the caveat, and the docs carry it on every surface that shows a command. One switch (CLI_RELEASED) silences all of them at launch, and a test refuses to let one move without the others. Affects all components only in what the brief says about installing them; no item's props, CSS or rendered semantics change.
• v0.2.0 · 2026-10-04 · ChangedEcho's home is echo-ui.com. The registry, the docs and the packages all move to it from echo.nawwara.studio. Nothing was published under the old host, so no echo.json anywhere points at it and there is nothing to migrate — this is the last release where that is true.
• v0.2.0 · 2026-10-04 · ChangedWeights, line heights, letter-spacing, z-index, border widths and icon sizes come from the theme scales in all components, with the old value as a fallback, so components keep working with echo-ui-core@0.0.1. Strays moved to the nearest step: most by under a pixel; HardwareButton icons are 14/16/20px (were 15/17/19).
• v0.2.0 · 2026-10-04 · FixedContent now reflows into a 320px screen (400% zoom) and survives a doubled browser text size (WCAG 1.4.10, 1.4.4), across all components. Select's 180px floor, NumberField's readout, Segmented and Steps as flex items, EmptyState's grid columns, and Avatar's fixed-pixel disc all gave way; Panel counts its padding inside a width you set (box-sizing: border-box), so a <Panel style={{ width: 220 }}> is now 220px wide overall rather than 260px.