Framework · Motion & interaction · 3 min read
Stagger and sequence rules
Four rules for motion with more than one moving part (clear the old content, let one element lead, let its content follow in reading order, cap the stagger) and one sum that tells you how long people will wait.
- 1Clear
Old content leaves first, fast, all together.
No stagger on the way out - 2Lead
The touched element or the new container moves first and furthest.
The card, with its photo - 3Follow
Its content arrives a few tens of milliseconds later, in reading order.
Title, then text - 4Cap
Stagger only the first visible items; the rest arrive together.
Not fifty rows in a queue
Total time = gap × (items − 1) + one item's duration
Use it when
- A list, a grid of cards or a dashboard animates in.
- A card opens into a page and several parts move at once.
- A choreography looks lovely in the prototype and slow in the product.
How to use it
- Clear first. The old content leaves before the new arrives, fast and all together. Exits don't need to be read, so they don't stagger. Output: an exit with no delays.
- Pick the leader. The element the person touched, or the container of the new content. It moves first and travels furthest. Output: one named leader per transition.
- Let the content follow. Things that belong to the leader (its title, its text, its buttons) arrive a little after, in reading order: top to bottom, start to end, right to left in a right-to-left language. Output: an order and a gap of a few tens of milliseconds.
- Cap the count. Stagger the first few visible items; let the rest arrive together. Output: a cap, for example the rows above the fold.
- Do the sum, then write the timeline. Total = gap × (items − 1) + duration. If the total passes about half a second, shorten the gap or the cap. Write it as bars in milliseconds for the developer. Output: a timeline with a total.
Worked example
In a task app for small teams, switching boards shows the first column as a list of six tasks. The first version staggers them 150 ms apart, each taking 250 ms: 150 × 5 + 250 = 1,000 ms before the last task has arrived. People tap a task that isn't there yet.
The designer applies the rules. The old board clears in 150 ms, all at once. The column leads. The tasks follow 40 ms apart: 40 × 5 + 250 = 450 ms, the same numbers as the lesson's demo. When a column has thirty tasks, only the ones on screen stagger; the rest are already in place when the person scrolls. With reduced motion on, the rows fade in together, with no movement and no delay.
Watch out for
- No leader. Everything moves at once and nothing tells the eye where to look.
- Long staggers on long lists. The last item arrives seconds later, and people start waiting for the motion.
- A staggered exit. Leaving takes as long as arriving. Exits go together and fast.
- Content before its container. Text that arrives before its card seems to float in from nowhere.
Template
Fill this in for every transition with more than one moving part.
Transition: ...
Exit (together): ... in ... ms
Leader: ... (moves first, travels furthest)
Followers, in reading order: 1 ... 2 ... 3 ...
Gap: ... ms Cap: first ... items, the rest together
One item's duration: ... ms
Total = gap x (items - 1) + duration = ... ms (over ~500 ms? shorten)
Reduced motion: ...
- Designing Interface AnimationVal HeadBook · 2016 (Amazon)
- Disney Animation: The Illusion of LifeFrank Thomas and Ollie JohnstonBook · 1981 (Amazon)
- Executing UX AnimationsNN/g (external site)
- The UX in Motion ManifestoIssara Willenskomer (external site)
- transition-delayMDN (external site)
"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.