Designed for teams building voice-first interfaces and audio assistants.
Users need to know whether a microphone is ready, audio is being captured or a response is playing. Give each phase a recognizable silhouette and define transitions for permission denial and silence.
What we can build
- Conversational status motion.
- Audio-reactive control design.
- Muted and unavailable states.
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:
- phase: conversational lifecycle.
- level: normalized audio amplitude.
- muted: persistent microphone state.
These are proposed control names and behaviors, not an existing Rive asset. The final file determines the actual property and state names.
Integration considerations
Feed a smoothed amplitude value from the application if audio reactivity is required. Animation does not record audio or manage microphone permissions.
Review the behavior
Test silence, a noisy input, permission rejection and rapid mute toggles. Status text must remain available without motion.
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
Does animation process microphone audio?
No. The product supplies microphone state and any amplitude data. Audio capture and permission handling remain application responsibilities.
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.