Who this is for: Designers planning interface motion for a landing-page hero.
What to prepare
- Landing-page headline
- One verified product action
- Start and result states
- Loop reset treatment and still frame
Tie the loop to one page promise
Read the headline and describe the single product behavior that supports it. If the headline concerns request ownership, a color-theme animation is visually active but irrelevant. Choose a record, control and result that all belong to the same promise.
The loop should remain understandable if a viewer arrives halfway through it. Keep the object identity and an explanatory label visible. Do not rely on a spoken opening that may have already passed.
Illustrative loop-boundary worksheet
For a fictional assignment tool, the page sentence is “Give each request a visible owner.” Use clearly marked sample request R-019 and supplied before-and-after states. This 15-second outline is a planning exercise.
- Entry, 0–4 seconds: R-019 appears with Owner: Unassigned. A stable heading names the assignment task.
- Action, 4–9 seconds: show the verified owner selection and save behavior. Omit unrelated navigation only when setup is stated nearby.
- Result, 9–13 seconds: Owner: Example reviewer is readable beside R-019. Hold this state without additional effects.
- Reset, 13–15 seconds: cut through a neutral title or clearly labeled replay boundary before returning to the initial sample state. Do not animate a saved assignment mysteriously reversing.
Design the page and video together
Keep the headline, video label and important interface text from competing at the same moment. If page copy explains the benefit, the video can focus on the action. Leave room around the featured control for annotations without covering it.
Provide a representative still frame and a page experience that does not require the animation to communicate essential information. Player and reduced-motion behavior need implementation review in the actual website; a storyboard alone does not verify those behaviors.
Simplify when the loop becomes a tutorial
If assignment requires several screens, select a smaller observable moment or use a longer standalone demo linked from the hero. Do not fake a one-click path to satisfy the loop duration.
Inspect the final-to-first cut repeatedly during review. A clean loop is not merely a matching color palette; it preserves the viewer’s understanding that a sample demonstration is restarting.
Review checklist
- The action supports the page’s main sentence.
- The result is readable before reset.
- Reset cannot be mistaken for product undo behavior.
- The surrounding page retains essential meaning without motion.