Creates emotional continuity
A companion turns scattered rewards into a visible relationship over time.
warming the kiln…
Avatar gives the system a face. Users see a companion grow, equip items and react to their milestones while your app keeps canonical state on the server.

Each primitive exists to support retention, clarity or trust. No decorative points system required.
A companion turns scattered rewards into a visible relationship over time.
Outfits, stages and badges can render inside Hatched widgets or your own UI.
The same avatar state can appear in onboarding, lessons, profiles and recap emails.
Product teams control the concept. Engineering sends events and embeds the result.
Create or import a user and let Hatched initialize their companion state.
Skills, badges, tokens and items update the avatar state after events.
Use widgets or API reads to show the same state across product surfaces.
The useful part is not the label. It is the way avatar turns product activity into a concrete state change users can understand.
{
"user_id": "u_mert",
"stage": 3,
"trigger": "total_skill_level",
"unlocked_slot": "accessory"
}Marketplace, evaluation, avatar, badges, skills, tokens, path and streaks share the same event and state model.