Easing
Easing is the timing curve that sets how an animation speeds up and slows down.
cubic-bezier()A real example
A panel enters quickly and comes to a soft stop. Its exit is shorter and more direct.
Main parts
- 01Trigger
- 02Property change
- 03Timing model
- 04Reduced-motion result
Use it when
Use easing when speed should show weight, direction, or purpose.
Do not use it when
Never use the same large bounce for every interaction.
Name used in code
cubic-bezier() Before you ship
Check content order, shared design values, component consistency, contrast, zoom, and layout changes by screen size. Verify every theme, language, and state. If there is motion, offer an equal reduced-motion experience.
Outcome: Use or define Easing to make the visual experience clear and easy to use. User context: A panel enters quickly and comes to a soft stop. Its exit is shorter and more direct. Design concept to apply: Easing. Why it fits: Use easing when speed should show weight, direction, or purpose. Do not use it when: Never use the same large bounce for every interaction. Design requirements: Set the content order, shared design values, and reusable components. Define how the layout changes by screen size and state. Keep useful design choices separate from decoration. Inclusion and resilience: Check contrast, zoom, languages, themes, and reduced motion when needed. Do not use color or effects as the only way to show meaning. Acceptance criteria: The design stays clear on phones and desktops, at zoom, in every theme, and in all supported languages. Interactive states stay clear and consistent. Evidence and limits (evidence boundary): A formal document may still be a draft, release candidate, or final version. Check its status and browser or platform support. Unknowns to confirm: Brand limits, amount of content, supported themes and languages, target devices, and design-system rules.
Check this request
Review the current use of Easing. Definition: Easing is the timing curve that sets how an animation speeds up and slows down. Release checks: Check content order, shared design values, component consistency, contrast, zoom, and layout changes by screen size. Verify every theme, language, and state. If there is motion, offer an equal reduced-motion experience. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.