An Emotion-Based Retention System for Kids

We had built an AI companion children could genuinely talk to (that story is its own case study). But a good conversation is not a reason to return. Most children's products solve retention with the standard toolkit: streaks, daily rewards, loss aversion, notification pressure. For a product aimed at 6–12 year olds, we considered that toolkit off the table.

So the question became: could retention emerge from attachment instead of compulsion? If a child came back because they missed a friend (not because a streak would break) the product would retain for the right reasons.

An extroverted child warms up through banter and competition. An introverted child needs space, and finds pressure in exactly the things the extrovert enjoys. A single bonding path would have worked for one group and quietly pushed the other away.

So the experience opened with a lightweight questionnaire (woven into the story so it never felt like a form) that classified the child along an introvert–extrovert axis. That classification then shaped the activities offered, how Dux initiated interaction, and how much conversational pressure the experience applied.

The classification fed directly into which activity carried the bonding. Both games were designed around the same goal (time spent with Dux) but with opposite social pressure profiles.

Standard game progression is about the player getting stronger. That frames the companion as a tool. We inverted it: the skill tree belongs to the friendship, not the player. At its centre, the child's hand and Dux's paw meet. The left branch grows the child's abilities; the right branch grows Dux's, and the child chooses where to invest, including in their friend.

Spending your progress on someone else is a small act of care. Repeated over sessions, it does what no streak counter can: it makes the relationship itself the thing that grows.

Friendships live somewhere. The Dreamer's Lodge gave the relationship a home: a warm, explorable space where activities, quests, and conversations all happened. Children weren't opening a chat UI. They were visiting a place where their friend lived. Returning to the app meant returning somewhere, to someone.

We expected the Lodge to compete for attention. A new environment usually wins against a character. It didn't. In session after session, children explored briefly and then returned to interact with Dux. The attachment loop was doing exactly what it was designed to do: the relationship, not the content, was the draw.

The experience shipped as an A/B test on the Atlas Keeper platform (the traditional experience against the Dux companion experience), putting the attachment-versus-compulsion question in front of real usage data.

Inside a session, the attachment loop worked: children chose Dux over an open world, and talked to him before anyone taught them how. But it didn't convert into retention. Over the run, the numbers came in below the conventional experience, and the reasons were more instructive than any success would have been.

The lesson I took: attachment can be designed, but it can't be rushed, and it isn't automatically stronger than the habits it's up against. If I ran it again, I'd design for the arc of a relationship across many short sessions, not the weight of a single one.