- ~10x → normal · Render failure rate after the After Effects 4.0 launch
- ~13% · After Effects users who bring Lottie back as editable layers
- ~14,000 a month · Lottie Creator edits opened from the plugins
The same motion, wherever you make it and wherever you use it
LottieFiles is a global platform for making and using Lottie animations. Designers work in After Effects, Figma and Canva, developers in VS Code, and motion designers in Lottie Creator. My job was to connect those tools into one motion system.
- LottieFiles plugin UX for each platform: After Effects, Figma, Canva, VS Code and more
- The links between the plugins and Lottie Creator
- Cross-platform support for animation and vector graphics, with the dotLottie and ThorVG engineers
- A connected experience for finding and using community animations across platforms
- A motion library (Motion System) for enterprise and paid-plan users, with official docs and onboarding
Files traveled, but the team's motion rules didn't
Lottie made animations play on many platforms, but it didn't carry the team's motion rules, such as its easing and presets, along with them. The same team, working across Figma, After Effects, the web and Creator, had to recreate and re-explain its easing, presets and assets in every tool.
Just as brand colors and type are shared through a design system, motion needed reusable units with names and clear uses. But first, people had to trust what each tool produced.
Obstacle 1: render failures up 10x right after launch
My first big project after joining LottieFiles in 2024 was the After Effects plugin 4.0 relaunch. It looked like a UI refresh, but underneath it swapped in a new rendering toolkit.
After launch, real work files exposed edge cases the clean test files never had, and the render failure rate rose to about 10x. With no dedicated QA, I kept meeting key customers to look at their real files and results, and sorted the failures into reproducible types. We decided what to support first by how often it was used, how much it affected the result, and whether it could play the same way across platforms.
While the dotLottie and ThorVG engineers widened rendering support, I turned real cases into priorities and expected results. More visual effects and vector graphics, including Gaussian Blur, now play the same on web and apps, and the failure rate came back to normal.
Obstacle 2: values lost every time work moved between tools
After Effects, Figma and Canva each hold animation in their own way. To bring a Lottie into one of them, we had to rebuild it into a consistent shape that fit that tool's spec, and complex values such as gradients were often lost along the way. An animation made in one tool looked different or couldn't be edited again in another, so the link between Lottie and each tool grew very weak. I focused on keeping values and the flow of work intact as people moved between tools.
- Lottie you can edit again: I designed an Insert experience that rebuilds exported Lottie and SVG as After Effects layers and keyframes. Instead of promising a perfect round trip, it shows clearly what comes in and how far it can be edited. About 13% of users use it.
- One Edit button in every tool: each tool had its own path to advanced editing. I unified them into a single Edit action on the animation preview that hands off to Lottie Creator for detailed editing, state machines and motion tokens. The plugins now open Creator edits about 14,000 times a month, especially from tools that don't handle keyframes themselves.
- Community animations: finding and using community animations, once separate on each platform, joined the same flow.

Not everything belonged in the plugins, either. Detailed editing continues in Lottie Creator, and versioning and CDN delivery continue in the web workspace, so an animation started in one tool never has to be rebuilt to go further.
I also made the very start of an animation happen inside the tool. AI Vectorizer turns images into editable vector layers so people can start animating right away, but it was easy to miss and most people never found it. So when an image layer is selected in Figma, the plugin shows Vectorize as the primary action instead of Export, one click away. That showed the feature could serve every Figma user, so we also launched it as a standalone plugin, AI Vectorizer, which brought in organic users beyond Lottie.
Explore AI VectorizerObstacle 3: the same easing, used differently in every tool
The last step was letting every tool use the team's motion rules themselves. Motion System started on the web as a library of a team's easing, presets and assets, and I owned how that library is used and edited inside each tool.
One standard didn't mean one interface. Figma applies easing to prototype interactions, After Effects to keyframes, and developers need values they can use in code. So one library is applied to selected interactions in Figma, to selected keyframes in After Effects, and as values that go straight into code in VS Code. Values changed mid-project can be published back to the team straight from the plugin.
Motion tokens and state machines widened what could be reused. Properties such as color, text and position get names so they can be swapped, and states and transitions travel with the animation inside .lottie so it can react to clicks and hovers. In the plugins, these start from concepts designers already know, like Figma variables and prototypes, rather than from the file format.
After launch, I put as much care into docs and onboarding as into the features. Several large Korean companies in particular had to fit a new motion system into their existing production and approval processes. Their recurring questions, such as which values to define first, how to move existing After Effects assets, and how designers and developers share the same names, fed product improvements and the official docs.
Where it stands: motion rules set once, used in every tool
Teams now build a motion system on the web, use it in Figma, After Effects and VS Code in each tool's own way, and move to Lottie Creator when they need deeper editing. The animations they make play the same across platforms.
The plugins, the web and Creator are no longer separate features. Together they form one flow where a team sets its motion rules once and uses them in any tool.
State Machines documentation