A playful grocery-tracking concept and a Community note about branding working with hero animation made me notice the same useful pattern: motion feels most helpful when it demonstrates one product behavior. The useful balance is giving the animation enough character to express the brand without asking it to dominate the hero. For a playful grocery app, I would show one item being tapped, moving into the tracked list, and receiving a brief confirmation. The headline and call to action can stay still and readable around it. Rive's current docs describe state machines as the logic behind interactive animation. They also note that reduced motion is not applied automatically, so it needs to be authored and passed into the file deliberately. My handoff would name the behavior first, reduce it to rest, action, and confirmation, then document the trigger and response. I would also include the exact state-machine name, the reduced-motion route, and a static fallback agreed with the developer. The fallback before the runtime loads or if it fails still needs a clear implementation decision. That small boundary aside, the result is a hero that explains the app's main action without adding another line of copy. What is one product behavior you would demonstrate through motion in the hero rather than explain with another line of copy?