What needs to be in your app for the animation to play?
Give the builder a file and a player that supports it. Lottie JSON describes a single animation. A dotLottie file can bundle multiple animations and assets, and needs a dotLottie-compatible player. The file alone does not make the browser draw the motion.
Decide whether your app will host the file or depend on a hosted link. Keep your own approved copy and the player version you used. LottieFiles’ dotLottie web package lists MIT for its code. That license is separate from the animation’s terms.
Which terms apply to the animation you want to publish?
Check how you got it. Public files covered by the Lottie Simple License allow commercial use under that license. Keep the same license terms with that animation when you publish, publicly display, perform or distribute it, including a version you modified. Premium assets have separate terms.
LottieFiles’ plan guide treats commercial work created or edited through its services separately. It excludes free public animations from that plan restriction and identifies commercial-capable service plans. Confirm the asset and plan terms for the work you intend to ship.
What should remain visible if motion is reduced or the file fails to load?
Keep important feedback in text. A success animation can accompany “Saved,” but the same message should appear if the player cannot load or motion is turned off. Keep the source, intended export, permission details and a static fallback with your handoff.
How should a successful save look with and without the animation?
Sketch a fictional Save button and the screen after it succeeds. Do this on paper.
- Draw the usual screenShow the text “Saved” and mark where the animation can play.
- Draw the fallbackRemove the animation. The message should still appear and nothing important should move or disappear.