F7.10.1Stacked motion extends waitdesign

Stacked motion lengthens total wait

Aliases: chained motion · stacked wait · staggered entrance

What it is

Enter, then rows one by one, then the button springs — three clips in series, and the user waits for the sum, not the longest piece. Stacking is serial in time: each clip is “reasonable,” together they become an extra wait. This is not several clips fighting the main thread at once — that drops frames; this adds clock that must be watched to the end.

Why it happens

Orchestration tools default to sequences: container first, children staggered, footer last. The intent is hierarchy; the side effect is pushing the interactive moment to the last item’s landing. Total wait ≈ Σ(each duration + stagger delay). A design review looks clip by clip, each a harmless 200 ms; the task path on wall clock has already burned a second.

There are hidden segments too: page transition finishes, then internal entrance, then taps are allowed. Clocks butt end to end, none overlapping the load. Abuse happens when “each piece has a reason” — the reasons hold locally, the sum has none.

Where it stops holding

  • Truly parallel clips (arriving together) do not lengthen wall clock; the cost moves to the performance ledger.
  • A one-shot ceremony (first completion, empty-state welcome) may be serial if it is skippable and stays off the everyday path.
  • A stagger of tens of milliseconds with a still-short total is not felt as a chain; the harm is perceptible segment-by-segment waiting.

Applying it

  • Draw the path on wall clock: tap to tappable, mark every animation, and fold what can run in parallel into one window.
  • Do not wait for every row to finish entering before scroll and taps work; interactive once the first screen is stable.
  • Check: record a timeline of “open page → tap the primary button.” If tappable equals the sum of the clips, stacking is levying a tax.

Related

  • Same group: F7.10.2 Repeat actions by expert users are slowed by motion · F7.10.3 Motion should yield to a faster next action
  • Nearby: F7.06.2 The cover must not outlast the real delay · F7.12.4 Simultaneous motions stack cost beyond a single-motion budget
  • Search terms: stacked motion · staggered entrance · time to interactive

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/F7.10.1