Designed for product teams adding a chat assistant to an existing interface.
Typing loops can mislead when a request fails or a stream stops. Build a small vocabulary of waiting, streaming, completed and failed states that follows the real response lifecycle.
What we can build
- Message status transitions.
- Retry and completion feedback.
- Compact assistant presence.
The final deliverables are agreed during discovery. Source files, implementation support and additional platform variants are included only when explicitly scoped.
A clear control contract
Plan the animation’s public controls before producing a full motion library. A starting specification might include:
- requestState: pending / streaming / complete / failed.
- hasFocus: conversation focus.
- retry: deliberate user action.
These are proposed control names and behaviors, not an existing Rive asset. The final file determines the actual property and state names.
Integration considerations
Drive state from request and stream events. Keep essential messages in accessible HTML; animated text is not a replacement for readable chat content.
Review the behavior
Simulate a failed stream and retry. No completed state should appear before the application confirms completion.
From brief to handoff
- Define. Review your audience, key events, platform and asset requirements.
- Design. Approve the visual direction, key poses and transition rules.
- Build. Rig the artwork and author the agreed state system.
- Validate. Review an export against the acceptance sequence and target runtime.
- Handoff. Deliver the scoped assets, control map and integration notes.
Questions before we start
Can the mascot replace loading text?
Keep a readable status alongside the animation. This supports screen readers and makes errors understandable when animation is paused.
What should I include in the brief?
Share the target platform, screen dimensions, existing artwork, desired states and any runtime restrictions. A short recording of the current product is useful.
How are timing and cost agreed?
Scope depends on the artwork, state count, platform validation and revision needs. A defined brief comes before a project estimate.