← Back to the marketplace

Digital assets / CREAVA

Quiet Motion Timing Recipes

Creava Editorial$27 USD

Six small motion patterns described as editable timing data and practical notes: reveal, dismiss, rearrange, acknowledge, expand and pause. Each includes its purpose, trigger and a reduced-motion alternative. Use them as a starting point for design discussion, then test the behavior in your own interface.

Inside the scope

  • Six motion behavior recipes
  • Generic JSON timing definitions
  • Easing observation exercise
  • Interruption and repeat-behavior notes
  • Reduced-motion alternatives
A reveal recipe might describe opacity from zero to one over a short interval with a gentle ease-out. If motion is reduced, show the content immediately and preserve the same reading order.

Compatibility & delivery

Application-neutral data requiring implementation or manual adaptation. Not an After Effects preset, Figma plugin or production JavaScript library.

Reference data and explanation; no software integration or device-specific support is included.

This page provides scope information and a text preview. Listed files or individual review sessions are not automatically delivered by saving a selection.

PRODUCT IN CONTEXT / CREAVA EDITORIAL

A closer look at the fit.

A working situation

For a saved-item notification, compare a brief appearance change with a larger sliding motion using the same wording. Test repeated saves and a reduced-motion preference, then retain a version that communicates the result without blocking the next action. Document how the chosen recipe maps to actual states and what remains an implementation decision.

How should I choose between two timing recipes?

Use the movement's purpose as the criterion: a brief acknowledgement and a scene transition explain different things. Compare one property at a time with the same content, and note whether the choice improves clarity or merely adds atmosphere. Avoid treating a preferred duration as a universal rule.

Will the JSON implement reduced motion for me?

No. It is reference data requiring application-specific implementation. The browser preference can inform a reduced-motion path, but the developer must define and test that path. Preserve the meaning of state changes through stable content rather than assuming less movement automatically creates an understandable interaction.

FROM THE CREAVA TEAM

Product notes & questions.

Editorial explanations of the product scope, not buyer reviews.

Understanding motion recipes and specifications

Can I install the JSON file in an animation application?

The JSON is application-neutral descriptive data. It is not a native application preset or plugin. A designer or developer must interpret and adapt the settings to the tool or codebase where the motion will be implemented.

What is the difference between the two motion products?

The Timing Recipes offer six starting patterns and their purposes. The Handoff Specification helps document a particular design, including triggers, states, interruption behavior and a reduced-motion alternative. One supplies starting references; the other organizes the final decision.

Are the recommended timings suitable for every interface?

No. They are starting points for comparison. Test the motion in its actual context, including repeated actions, loading, interruption and reduced-motion settings, and change the values when the behavior calls for it.

CREAVA EDITORIAL / THE WORKING LIBRARY

A little more behind the work.

Briefs, creative decisions, production habits and practical answers from the Creava editorial desk.

Visit the library