Designed for app teams introducing a workflow or unfamiliar feature.
A timed onboarding video cannot respond to hesitation or completion. Design short sequences that advance with the user and remain understandable when a step is skipped.
What we can build
- Step-specific animation scenes.
- Forward and back transitions.
- Completion and skip behavior.
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:
- step: current onboarding page.
- direction: forward / back.
- complete: confirmed task event.
These are proposed control names and behaviors, not an existing Rive asset. The final file determines the actual property and state names.
Integration considerations
Navigation owns the current step. Keep instructions as native text and let the animation illustrate the action; avoid essential copy inside a canvas.
Review the behavior
Navigate backwards, skip the flow and resume midway. Each step should have a coherent resting pose.
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 onboarding work without autoplay?
Yes. Use static key poses by default for reduced-motion users and provide explicit progression through the same instructions.
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.