Developer handoff

Developer handoff is about giving the developer three things: the right file, the right link, and the right runtime.

Handoff checklist

1. Share the Workspace asset URL when the animation is saved to Workspace.

2. Confirm the output format: prefer .lottie; use .json for legacy lottie-web compatibility.

3. Tell the developer whether the animation is interactive.

4. Recommend the runtime that matches the format.

5. Include a note if the animation uses state machines or themes.

Runtime guidance

• Use a dotLottie runtime for .lottie files — the preferred format for compact files and advanced features like state machines, themes, and motion tokens.

• Use a legacy Lottie runtime for .json when the destination still depends on lottie-web style players.

• Interactive Figma exports require dotLottie and a dotLottie runtime.

What to avoid

• Do not send only a GIF if the developer needs production animation.

• Do not export an interactive prototype as Lottie JSON and expect interactions to work.

• Do not assume a player preview in Figma guarantees identical playback in every app runtime.

Related

• Choosing an output format

• Player controls

• Runtime compatibility