Skills
The weekly motion teardown: train your eye on the sites you admire
Taste in motion is trained, not born. A 30-minute weekly teardown of one animation you admire, with its real values in front of you, builds the eye faster than any course.
Writers get better by reading closely. Musicians get better by transcribing solos. Designers and developers who want better motion can do the same: take an animation you admire, pull it apart, and understand why it works.
Most people stop at admiring. They notice that a site feels premium, maybe save a screenshot, and move on. The skill grows when you go one step further and ask what exactly is happening here?
Why the real values matter
You can do a teardown by eye, and it is better than nothing. But by eye you will mostly learn what you already expected. The surprises, which are where the learning is, live in the numbers:
- The duration you thought was half a second is 280 ms.
- The "bounce" is not a bounce at all, but a curve that overshoots by a few pixels and settles.
- The items that seem to arrive together are 30 ms apart.
- The thing you thought was moving is mostly fading, with a tiny 8 px slide underneath.
The Capture Motion Chrome extension gives you those numbers. Click the element, trigger the animation, and the preview lists every animated property with its keyframes, durations, delays and easing. It reads CSS transitions and keyframes, the Web Animations API, GSAP and Lottie, so it works on most of the sites worth studying.
The 30-minute teardown
Pick one animation a week. A menu, a hover state, a page entrance, a toggle. Then work through five questions.
- What triggers it? Load, scroll, click or hover. Write it down; it shapes everything else.
- What moves, and in what order? Read the track list. Group tracks into "leads" (the first thing that moves) and "followers".
- How long, and why that long? Note the longest duration. Ask whether it suits how often people see it.
- What is the curve doing? Look at the easing for the main track. Is it a keyword or a custom
cubic-bezier()orlinear()? Where does it spend its time: fast start, slow finish? - What would break it? Imagine the stagger removed, or the curve swapped for
ease. That tells you which value is doing the work.
Write the answers in two or three lines. The writing is the part that makes it stick.
Feel it, not just read it
Numbers explain. Handling the animation teaches. Two easy ways:
- In Figma: copy the capture's JSON and paste it into the Capture Motion Figma plugin. It becomes a Figma Motion timeline in your file, where you can scrub it, change a delay and see the result.
- In code: use Copy for LLM, paste it into Claude or ChatGPT, and ask for a self-contained HTML file. Then ask the model to move the durations and curves into CSS custom properties at the top, so you can tune them in the browser.
Change one value, play it, change it back. Ten minutes of that teaches more than an hour of reading about easing.
Keep a teardown log
Save the best captures to My Gallery with names that describe the lesson, not the site: "Menu open, 30 ms stagger, overshoot curve, on click". Over a few months that list becomes your personal motion textbook, with real examples behind every rule you learned.
You will also start to see patterns across sites: similar durations for controls, similar curves for entrances, a habit of fading first and moving second. Those patterns are the craft. Once you can name them, you can use them on purpose.
Learn the motion, not the brand
A teardown is for understanding timing and choreography. The layout, illustrations and brand of the site you studied are still theirs. When you use what you learned, take the rhythm and the curve, and build the rest from your own product.
Where to look
Good candidates for a teardown are the interactions you use daily and never think about: a tab bar, a toast, a search field opening, a card expanding. If you want a head start, the Capture Motion gallery is full of tuned examples. Liquid Pill Nav, Voice Chat Expand and Storage Scanner each have enough choreography for a full session.
Try it now. Install the Chrome extension from capturemotion.dev, pick one animation you have admired this week, and answer the five questions. Capturing and previewing need no account.
Questions
How long should a teardown take?
About 30 minutes for one animation: capture it, answer the five questions, then change a value or two in Figma or code.
Can I reuse the design of a site I studied?
Use what you learned about timing and choreography. The layout, illustrations and brand of the site are still theirs.
