Figma Motion and the Return of the Flash Designer
I think Figma Motion is going to create a new breed of Flash designer.
Not Flash as in the old plugin. That era is gone. I mean the kind of designer who thinks in scenes, timing, interaction, code, and feeling at the same time. Someone who does not just make a static layout and hand it over, but understands how the interface should move, respond, and behave.
That kind of hybrid designer used to be more common. Flash, for all its problems, gave a generation of designers a place to make things that felt alive: websites, games, portfolios, intros, interactive stories, strange little experiments. It rewarded people who could move between visual design, animation, and logic.
Figma Motion could bring some of that energy back, but inside the modern product design workflow.
Adoption beats theoretical capability
The important thing is not that Figma has invented animation. It has not. Rive exists. Lottie exists. After Effects exists. CSS and JavaScript have always been there for people willing to write the code. The important thing is that Figma is where product teams already live.
There are always more powerful tools than the one everyone uses. But the tool inside the daily workflow has an unfair advantage. If motion lives next to components, variables, comments, Dev Mode, design systems, and product decisions, it stops being a specialist afterthought. It becomes part of how the product is designed.
That is why Figma Motion is interesting.
At Config 2026, Figma introduced Motion as a native timeline on the canvas. Designers can keyframe layers, adjust timing, use easing and spring controls, create animated components, work with motion variables, and comment at specific points in an animation. Developers can inspect the motion in Dev Mode, copy code in formats like CSS, JSON, React, and motion.dev, or pass motion context to coding agents through MCP.
That is more than a timeline. It is Figma trying to turn motion into a system primitive.
AI lowers the floor
AI makes this even more important. Motion design has a brutal learning curve. You can describe a nice loading state or a slick card transition in plain language, but making it feel right takes taste, timing, and a lot of tiny adjustments.
With the Figma agent, a designer can prompt a first pass, get real keyframes on the timeline, and then refine from there.
That will definitely create bad motion. Lots of it.
But it will also create motion literacy. Designers who would never open After Effects may start to understand easing. Designers who would never write animation code may start to understand why a transition feels cheap. The floor gets lower, but for the people who develop taste, the ceiling gets higher.
Rive and Lottie still matter
This does not mean Figma Motion replaces Rive or Lottie.
Rive is still the stronger tool when animation is tied to real product behaviour. Its state machines connect animations to logic, inputs, transitions, and runtime states. If you are building game-like UI, complex interactive components, or motion that needs to run as part of the product itself, Rive is built for that mental model.
Lottie has its own lane too. It is lightweight, familiar to motion designers coming from After Effects, and has a big ecosystem around web and app delivery. LottieFiles is also pushing further with Lottie Creator, state machines, AI-assisted keyframes, and dotLottie workflows.
So Figma is not killing those tools. It is moving the centre of gravity.
For a button interaction, a screen transition, a loading state, a piece of branded product motion, or a reusable motion rule in a design system, Figma suddenly becomes the obvious place to start. The animation is attached to the component. The developer can inspect it. The agent can help generate it. The conversation happens in the same file.
The harder question
The future version of this is not simply “export my animation”. It is “translate this whole experience”.
Multiple scenes. Real product states. Data. Responsive behaviour. Conditional interactions. Shaders. 3D transforms. Motion that changes because the user, the content, or the system changes.
Figma is clearly moving in that direction. Config 2026 also brought shader effects and fills, code layers, deeper agent capabilities, MCP integrations, and 3D transforms. But those pieces are still uneven. Shader handoff is not yet as clean as normal Dev Mode. Code layers are still in closed beta. The full production interaction engine is not here yet.
That is why the interesting future is not about who “wins” between Figma, Rive, and Lottie.
It is about the kind of designer these tools create.
Figma Motion will not make everyone a motion designer. But it will make motion harder to ignore. And for the designers who lean into it, it could reopen a space that has been missing for a while: a hybrid creative space where design, animation, systems, AI, and code are not separate handoffs, but parts of the same thought.
That is the new Flash designer.
Not someone who just knows how to keyframe.
Someone who can design the object, animate the object, understand the system around it, and still make the whole thing feel good.