Behavioral motivation before adding effects

These examples and illustrative results are independently authored teaching materials, not measured model results.

Use case

Saving an item moves it to the top of a favorites list. You are considering motion to show where it went, instead of animating everything because a library is available. Success, failure and reduced-motion states all need meaningful feedback.

Mechanism

Before adding an effect, state the change it communicates. Here, movement only shows the saved item’s old-to-new position; informational headings stay still. Failure preserves position. Reduced motion uses an immediate update and textual feedback. Render and inspect the states rather than treating animation parameters as proof of working behavior.

Bad example

Animate the favorites list above. Since an animation library is installed, continuously float headings, cards and buttons. Play the same effect when saving fails.

Good example

Add purposeful feedback to this favorites list. After a successful save, use one position transition to show the item moving to the top; keep the heading still. On failure, retain its position and explain the failure. Under reduced motion, update position immediately and preserve 'Saved' text. State each effect's communicative purpose, then implement and inspect all three states. Omit purely decorative perpetual movement.

Why the change matters

The bad motion is independent of the save result and does not explain the position change. Connecting an effect to a successful state creates distinct, inspectable failure and reduced-motion behavior rather than one decorative animation for everything.

Observable expectation

Exercise the same item under success, failure and reduced motion. Illustrative records show: success→top with one transition; failure→original position with an error; reduced motion→top and text without a position transition.

Keep headings still and avoid conveying status through motion alone. Cut-off transitions, movement on failure or reduced-motion loops fail the check. No real favorites service was implemented here.

Limits

A stated purpose does not establish that users understood the effect. Consider performance, focus and motion preferences; static feedback may be sufficient. Upstream intensity dials and library choices are not universal requirements of this method.