Cilantrobyte.

Tech Stacks · Frontend

Motion

Formerly Framer Motion — now the React animation default.

Category

Frontend

At the studio

Since 2021

Projects shipped

1 case study

Status

Active

(01) Our take

Motion (the library formerly known as Framer Motion) is how we handle anything more complex than a CSS transition. Its declarative API fits React's mental model cleanly, and the performance is better than writing imperative animations by hand.

We're careful with animation. A little goes a long way, and "everything reveals on scroll" is a design anti-pattern. Our house style is to use motion to guide attention to state changes — a tooltip opening, a drawer sliding in, a value updating — rather than to decorate idle content.

(02) What we build with it

Typical work

  • Page transitions and shared element animations
  • Gesture-driven interactions (drag, swipe, scrub)
  • Microanimations on form feedback and state changes
  • Orchestrated entrance animations for marketing sites

(03) How we engage

Engagement shape

Layered into any frontend project that needs interaction polish — not a standalone engagement.

(04) In production

Where we've shipped it

All case studies →

(05) Pairs with

Works well with

Technologies we reach for alongside Motion in most engagements.

Frontend

React

The UI library we'd still pick today.

Frontend

Next.js

The default for serious React applications.

Frontend

Tailwind CSS

The CSS framework that finally got out of the way.

Thinking about a Motion project?

Start a project →back to all stacks