The Pain We All Feel
If you’ve ever tried to prototype a micro-interaction in Figma, you know the drill:
-
Duplicate an artboard.
-
Nudge a layer.
-
Duplicate it again.
-
Repeat… 37 times.
Smart Animate is great for quick fades and slides, but the moment you need real control—timelines, easing, staggered keyframes—you’re back to brute-forcing screens or exporting to After Effects. Reusability? Practically a myth. Maintaining motion across a design system is a part-time job nobody asked for.
Our “What If” Moment
Last week’s Figma Config conference blew our minds with new dev mode upgrades, but it left one question hanging: Why is advanced motion still an afterthought?
At Revolt we were animating button states when someone blurted out, “What if animations just lived inside the component?” That one thought spiraled into a late-night whiteboard session and, ultimately, a proof of concept we’re calling Figma Motion.
Meet Figma Motion (Concept)
But… Does Figma Even Need This?
Short answer: Yes. Design systems matured from static style guides to dynamic, interactive ecosystems. Motion is no longer “nice to have”—it’s critical for accessibility cues, brand expression, and perceived performance. Yet our workflows treat it like a bolt-on effect. Figma Motion closes that gap.
What Happens Next?
We’re sharing this concept to spark conversation. If enough designers raise their hands, maybe Figma will take notice—or maybe we’ll build an indie tool that plugs the gap ourselves.
