Air vs LottieFiles
Side-by-side trajectory, velocity, and editorial themes.
Air pushes the DAM into Shopify, WordPress, and Chrome — and turns AI edits into reusable Skills.
Air is shipping in two clear directions at once. On the integration side, May brought a coordinated wave: Air for Shopify, Air for WordPress, and a Chrome extension for saving images straight into Canvases and Boards. On the AI Canvas side, Skills landed as a way to save any AI edit as a named, reusable workflow runnable across batches. Adjacent Canvas work — lighting changes, Edit Text via AWS Rekognition, perspective regeneration, Seedance 2.0 video — keeps filling out the generative toolbox.
Air is positioning itself as the brand-asset layer that lives wherever customers already publish — not a destination DAM you visit, but a Canvas you reach for from inside Shopify, WordPress, or a browser tab. The Skills release pushes Canvas from a per-image AI editor toward a workspace-wide automation surface, where edits are scripted once and reused at batch scale. The integration wave and the Skills launch are complementary: more surfaces to push Air-managed assets to, and more programmable ways to mass-produce them.
Expect the next quarter to bring more publishing-surface integrations — likely Webflow, Klaviyo, or a major social scheduler — and a programmatic Skills API so external systems can invoke saved workflows. Skills shareability across workspaces is the obvious second-order move.
LottieFiles ships an MCP server alongside generative tooling — Lottie Creator is becoming AI-native.
LottieFiles is shipping aggressively across three threads: AI authoring (Prompt to Vector 2.0, AI-driven scene generation), agentic integration (Lottie Creator now connects to Claude, Cursor, and any MCP client), and creator-tool depth (curved-path animation, freehand vector drawing, version history, intelligent keyframe simplification). The .lottie file format gained multi-animation support, and a Figma plugin now translates Figma prototype interactions into production animations.
LottieFiles is positioning Creator as the canvas where motion design and AI tooling meet — both as a generation source (text-to-vector, scene generation) and as a target other AI assistants can manipulate via MCP. The Figma interaction-to-animation feature suggests a deliberate strategy of importing intent from upstream design tools rather than asking designers to redesign in Lottie Creator. File format work (multi-animation .lottie, smaller files at same fidelity) keeps Lottie viable as the underlying motion-graphics format on the web.
Expect deeper MCP-driven workflows — agents that take a brief and produce a finished Lottie file inside Creator without human authoring — and additional importers from After Effects, Rive, or Spline. The Figma interaction bridge is likely to be replicated for other prototyping tools (Framer, ProtoPie). Generative motion is a strong candidate for next major surface.
See more alternatives to Air →
See more alternatives to LottieFiles →