Tally vs LottieFiles
Side-by-side trajectory, velocity, and editorial themes.
Tally adds PDF export, MCP polish, and editor ergonomics — bootstrapped grind, no big leaps.
Tally is in steady weekly-release mode. Headline shipping in April: one-click PDF export of any form submission (using the form's theme so output is on-brand and free), MCP integration improvements for AI-agent workflows, and editor productivity work — a floating table of contents on long forms, plus page-level conditional logic that landed in early March. The Trash modal got a redesign and a manual-empty option for compliance-conscious users.
Two threads run through the cadence: outputs (PDF export, themed templates) and editor scale (table of contents, page-level logic, MCP). Tally is rounding out the simple-form surface so it can stand in for contract/order-confirmation tools and so power users with 40-block forms can keep working in it. Bootstrapped pacing, no platform pivots — every release closes a specific user complaint.
Expect more output formats (signed PDFs with e-sig integrations, branded email confirmations) since the PDF release explicitly hooks into electronic signature workflows. The MCP work suggests more AI-driven form authoring or response handling is queued — easier to imagine "agent fills out a form" or "agent summarizes responses" than another form-design feature.
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 Tally →
See more alternatives to LottieFiles →