The snippets above show the interaction itself. They assume you have loaded lottie-web, created a player, waited for DOMLoaded and connected the variables to real controls. A production implementation also needs cleanup, error handling, accessible state and a reduced-motion fallback. The guide covers those boundaries.
A Lottie animation whose playback responds to input or application state. Hover, click, pointer position and scroll can choose when it plays, its direction, or its current frame.
Can the demos work on phones?
Yes. Hover has a tap alternative, the cursor demo has a slider, and buttons support touch and keyboard. Reduced-motion mode keeps static previews and working controls.
Are these original animations?
Yes. Every animation comes from Sergey Designer’s existing portfolio. These interaction wrappers are new demonstration interfaces, not claims about a particular shipped client flow.
Is the state demo a dotLottie state machine?
This demo uses a LottieFiles Interactivity chain with Lottie JSON and lottie-web. It is not an embedded dotLottie state machine; the implementation and delivery format are chosen for each project.
Can you build this into our product?
The animation and interaction specification can be scoped together. Share your framework, target devices, states and fallback requirements so design and implementation can be priced clearly.
Can I reuse these JSON files?
The library is for portfolio preview and scoping. Public preview does not grant a production license to reuse client work. Request a custom animation in your own brand instead.