Pave motion audit

Every place in the front end where something moves, read and scored against one motion language.

Real work · figures from the published write-up

The finding that started it

The same spinner ran at four different speeds.

01

How it was read

How it was read

Every stylesheet read, not sampled

Source: Pave motion audit, Quickbase, 2026. Figures as published in the write-up; internal names removed.

How it was read

One spinner, four speeds

One rotation, measured in each copy of the keyframes.

Source: Pave motion audit, Quickbase, 2026. Figures as published in the write-up; internal names removed.

02

What a finding looks like

What a finding looks like

Toast enter: today and proposed

Source: Pave motion audit, Quickbase, 2026. Figures as published in the write-up; internal names removed.

What a finding looks like

Eight characters per curve

Speed over time for each easing in the audit.

Source: Pave motion audit, Quickbase, 2026. Figures as published in the write-up; internal names removed.

What a finding looks like

Overlaps nobody saw in review

Source: Pave motion audit, Quickbase, 2026. Figures as published in the write-up; internal names removed.

03

Handing off the hero

Handing off the hero

The hero cut against the product

The marketing hero drifted all the time; the product grid mostly holds still.

Source: Hero animation handoff, 60-second recordings of both versions, every line position logged per frame.

What changed

One duration scale, one easing set, one spinner speed.