Designed for teams building rewards, streaks and achievement systems.
Rewards lose clarity when every action triggers the same celebration. Build a hierarchy from subtle progress to significant milestones, with limits on interruption.
What we can build
- Reward and milestone vocabulary.
- Streak transitions.
- Replay and duplicate-event rules.
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:
- rewardTier: celebration intensity.
- progress: earned completion.
- celebrate: one-shot confirmed reward.
These are proposed control names and behaviors, not an existing Rive asset. The final file determines the actual property and state names.
Integration considerations
Trigger only after the application confirms the reward. Animation does not calculate scores, update accounts or determine eligibility.
Review the behavior
Send duplicate reward events and check screen re-entry. The same earned reward should not create repeated interruptions.
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 you design the reward logic?
This scope covers how confirmed progress is expressed. Scoring and reward eligibility should be defined by the product team.
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.