A field guide to UI motion
Motion WordName the motion you mean, then build it right
You saw it somewhere - the bouncy thing when a popover opens, the scroll that resists and snaps back. Describe it in your own words and get its exact name from a 91-term glossary where every term plays live. Then turn that term into a build spec with the curve, duration and reduced-motion variant a strict review would accept.
1 Describe what you saw word-match free
The page's first guess - word-match, before any run
Pricing as soon as the session is ready...
The reply could not be read; here it is as it came:
The answer - none yet.
NOT ASKED YETThe page's check
The glossary, live free
Every term from the animation vocabulary, quoted as written, each playing on its own stage. Tap one to build it.
Saved
How it works
Name it. The page's word-match reads your words against the feel words for each term and shows its first guesses for free. A metered run reads for intent instead of keywords and returns the best term, one or two close alternates with how they differ, and a prompt phrase you can hand to a designer or an AI. Definitions always come from the glossary itself, never from the model.
Build it. The recipe card applies the build rules for free: the frequency gate (100+ times a day or a keyboard shortcut means no animation, ever), the duration range for the element, the curve token and the allowed properties. A metered run makes the calls - purpose, tool, from and to values, exit, reduced motion - and writes the code; the page then checks the reply against the tables (no scale(0), no transition: all, no ease-in, durations in range, reduced motion present) and plays it on a mock of your element. Watch it at 2x or 5x slower before you ship it.