Yoggi

We've been iterating on Yoggi for a while now, and just like a lot of founders here, the small details ended up mattering more than the big features. Some of these took a day to build, others took much longer to get right, but all of them changed how parents and kids actually experience the product. Here's what stood out:

• Immediate value before any signup. Parents can send a few real messages to Yoggi and see exactly how she responds, including on harder topics, before ever creating an account. No signup wall blocking the first "aha" moment. Trust builds first, the account comes after, framed clearly as just a way to save what they already tested.

• Status instead of silence. A simple "Yoggi is thinking" indicator during a response might sound trivial, but for a 6 year old waiting for an answer, a blank screen reads as broken. A visible sign that something is happening removes the confusion.

• One clear action per screen. Kids at this age can't parse a busy interface. Big buttons, one obvious next step, minimal text. If a screen makes an adult pause to figure out what to do, it makes a child give up.

• Voice as a first class input. A lot of our users can't read or write well yet. Making voice input and voice playback fully native to the experience, not a bolt on feature, opened the app to a much younger age range than a text first design would have.

• Progress that only ever goes up. Trophies unlock permanently and never get taken away. No streak to lose, no countdown, no punishment for missing a day. Kids come back to grow a collection, not to avoid losing one, which turned out to matter a lot for anxiety around the app.

• Suggested replies for kids who can't type fast. One tap responses appear only when they make sense, during an interactive story or after a simple yes or no question, so a child can keep a story moving with a tap instead of typing. We were careful to not show these during normal free flowing conversation, so the AI never feels like it's steering the conversation for its own convenience.

• Explicit boundaries stated out loud. Yoggi always says she's an AI when asked, and redirects to a trusted adult when a conversation calls for it. We expected this to feel like a limitation. Parents actually told us it's one of the main reasons they trust the app enough to let their kid use it daily.

None of these are flashy. But together they're what gets mentioned by parents when they tell us why they kept using it.

____

If you're building for a young or non technical audience, what's the smallest change that had an outsized effect on how people actually used your product?

There's an easy trap when you build anything for kids with a chat interface: optimize for engagement and you'll get engagement, but you might get it by making the AI feel like a friend they need rather than a tool they enjoy. That's the opposite of what we want with Yoggi.

So every hook we build is tied to something the child does, not to the AI itself. Trophies for exploring topics, a gallery of drawings they've created, daily quests, streaks tied to activities. We want kids excited to open the app because there's a new story to continue or a badge to unlock, not because they miss talking to "her."

On the AI side itself, Yoggi always says clearly that she's an AI whenever asked, never pretends to be a real friend or a person. When a conversation goes somewhere that calls for an adult, she redirects the child toward talking to their parent instead of trying to be the solution herself. And rather than just answering questions, she leans socratic: asking a child what they think first, nudging them to reason it out, instead of just handing over the finished answer.

It's a harder design problem than it sounds. Kids love instant gratification, and an AI that just gives you the answer feels great in the moment. But building genuine curiosity and independent thinking, instead of dependency on an entity that flatters them, is the actual bet we're making with this product.

Would love to hear from anyone else building for kids: how do you think about the line between "sticky" and "healthy" engagement?

We just crossed our first 100 free users, and the thing that's genuinely surprised me isn't the number, it's the pattern of return usage. I expected mostly one off questions and general curiosity chat. Instead, based on parent feedback and usage patterns, a good chunk of the kids coming back day after day are treating Yoggi as an ongoing storytelling companion, picking up an imaginary world across multiple sessions instead of asking one question and leaving.

That's exactly the kind of engagement we designed for: a tool that sparks a child's own imagination rather than one that does the thinking for them.

Still very early days, small numbers, lots to learn. But if this is what happens at 100 users with almost no polish yet, I'm excited to see how it holds up as we grow.

If you're building anything for kids, what's the most surprising way your early users actually used your product versus what you expected?

A few months ago I read about kids forming deep emotional attachments to AI chatbots, some to the point of real distress when the app changed or went down, because at that age they genuinely can't tell the difference between a friend and a very convincing pattern of words. That stuck with me. Kids are already meeting AI today, on tools built for adults, with no framework, no supervision, and nobody explaining to them what they're actually talking to.

I didn't want that to be my own kid's first experience with AI. So I built Yoggi, a conversational AI companion designed specifically for children aged 3 to 15, with parents in the loop rather than locked out. It always identifies itself as an AI when asked. Every message is screened in real time, and if something concerning comes up, the parent gets an alert by email immediately, not days later. There's a daily message limit set by the parent, and a nightly summary of what the child talked about and how they seemed.

The goal isn't to give kids a smarter toy. It's to make sure their first contact with AI happens somewhere safe, age appropriate, and supervised, instead of alone on a platform that was never built with them in mind.

Curious how other builders working with kids or sensitive audiences think about this. Where do you draw the line between giving a child a useful tool and protecting them from getting emotionally hooked on it?