All case files

Series C, E-commerce

Checkout motion system

Checkout motion system

Checkout motion system

Defined a motion language for checkout and shipped it as twelve reusable tokens across web and app.

Role

Motion and design engineer

Team

Checkout squad of 6

Timeline

4 months, 2024

View live

Checkout motion system: product interface

+6.2%

checkout conversion

12

shared motion tokens

Built with

Figma, React, Motion, Lottie

The problem

Checkout felt abrupt. Errors appeared without warning, totals jumped around, and web and app animated the same moments differently.

Constraints

Checkout is the riskiest page in the business, so every change shipped behind an A/B test, and motion couldn’t slow anything down.

Design decisions

Motion should explain cause and effect, never decorate. I mapped every state change and gave each one a single, consistent behaviour.

What I built

Twelve duration and easing tokens shared by web and app, plus React primitives that use them by default, documented in Storybook.

Trade-offs

We dropped a playful success animation the team loved because it added 400ms to the confirmation. Fast beat fun.

The result

Checkout conversion rose 6.2% in an A/B test, and the motion tokens now drive animation across the whole product.

What I’d do differently

I’d test reduced-motion users as a separate cohort from the start instead of adding that check at the end.

P.S.

If your Figma file and your product have drifted apart, let’s fix that.

Twenty minutes, no deck. Bring a screen you’re stuck on and I’ll tell you how I’d design and build it, even if we never work together.

© 2026 Noor Avila. Designed in Figma, built in Framer.

Back to top

Create a free website with Framer, the website builder loved by startups, designers and agencies.