Designed for hardware teams developing screen-based desktop companions.
Robot expressions must remain readable at the actual screen size and viewing distance. Build eye and mouth poses around the display shape rather than shrinking a desktop character onto a device.
What we can build
- Screen-specific eye and mouth library.
- Idle, attention and recovery expressions.
- Display-safe layout variants.
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:
- gazeX / gazeY: eye direction.
- expression: named face state.
- blink: one-shot 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
This service covers 2D display animation. Confirm operating system, renderer, GPU, memory and runtime support before selecting Rive; motor control and embedded firmware are separate.
Review the behavior
Review on the target display at typical brightness and distance. Test clipping, idle power behavior and recovery after the display wakes.
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
Will it run on my robot?
Compatibility depends on the device display stack and available runtime. Share the hardware specifications before committing to an animation format.
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.