Lottie Creator 2.0 — LottieFiles’ browser-based vector animation tool — landed at the top of Product Hunt on July 28, pitched with the line “After Effects for the web, built on Lottie.” The claim is bolder than the usual web-tool marketing, and the release backs it with a fuller timeline editor, an AI assistant, and, most consequentially, a visual State Machine system that turns an exported animation from a linear clip into something that reacts.
The handoff problem it’s aimed at
The standard Lottie pipeline has been: animate in After Effects, export via a plugin, hand the JSON to a developer, discover in review that a timing or easing choice doesn’t survive contact with the product, go back to After Effects. Every iteration crosses a tool boundary and usually a team boundary.
Creator’s answer is to put design, animation, and export in one browser tab — no install, nothing to license per seat, and a shareable URL instead of a project file. That’s a familiar web-tool argument, but motion design is a case where it bites unusually hard, because the artifact being handed off (a JSON animation) is code-adjacent and the feedback loop is long.
State Machines are the actual news
The more interesting addition is the visual state machine editor: define states and wire up click, hover, and event-driven transitions without writing code, then ship the behavior inside the animation file itself. That reframes what a Lottie is. A conventional Lottie plays; a state-machined Lottie responds — a toggle that animates into its checked state, an icon that reacts on hover, a loader that transitions to a success pose when a request resolves.
For teams, that’s a real reallocation of work: the interaction logic that previously lived in application code, written by a developer interpreting a designer’s intent, can now be authored by the person who designed the motion. For the trade-off, see below.
The rest of the 2.0 surface
The release also brings a Motion Copilot AI assistant that generates shapes, text, gradients, layers, keyframes, easing, and looping motion from a description; Motion Tokens and a Motion System for consistency across a library; multi-animation dotLottie files; real text layers; and a growing plugin set. dotLottie in particular is a sensible container story — bundling several animations, and now behavior, in one compressed file instead of shipping a folder of loose JSON.
Where to be skeptical
“After Effects for the web” is a positioning statement, not a feature-parity claim; After Effects remains a far deeper compositing and effects environment, and complex motion work will keep living there. Prompt-generated motion has the same failure mode as prompt-generated everything else — plausible output that needs an experienced eye to fix, which is fine if you have one and a trap if you don’t. And moving interaction logic into a design file is genuinely useful right up until nobody on the engineering side can find where a behavior is defined.
Those caveats aside, the direction is right: the web’s most widely deployed animation format finally has a first-class authoring tool that speaks its own native language, including the interactive parts.