What Comes Next

Ideas compatible with the principles, parked until the V1 pillars are solid.

How ideas earn a place here

This page is a parking lot, not a roadmap. Nothing on it is committed, scheduled, or promised — it exists so that good ideas have somewhere to wait without quietly leaking into V1, and so that bad ideas get told no in writing.

Admission works like a test with two parts. First, an idea must pass every one of the company principles, asked as plain questions: Does it keep parents in charge without turning them into wardens? Does it add calm audio value without pulling the kid’s eyes to the canvas? Does it build independence rather than another distraction loop? Does it keep communication inside the parent-approved circle? Does it stay honest about location — live-ish, never more? Does it still work with no internet where that matters? One failed question means no slot.

Second, an idea must never cross a refusal on what we are not. The principles bend ideas into better shapes; the refusals are a wall. An idea that only works by adding a browser, a feed, a camera, or an engagement mechanic is not parked — it is rejected, and it goes in the list at the bottom of this page instead.

Even a passing idea waits. The V1 “Daylight” pillars come first — whitelist calls and voice notes, live-ish location, local-first listening, and the yoyopod app’s five jobs — and nothing here gets built until those are solid in real families’ hands, not just solid in a demo.

Parked ideas

Each of these has passed the test and is waiting its turn. Every one of them stays whitelist-only and parent-managed if it ever ships.

Walkie-talkie groups — push-to-talk voice among a handful of already-whitelisted contacts at once, so cousins can chatter like a convoy; parked because group audio raises pile-on and moderation questions that one-to-one Talk does not, and Talk must be boringly reliable first.
An audiobook store — a curated catalog of longer titles for parents to buy and load alongside music and stories; parked because a storefront pulls the product toward browsing and buying, and the local-first library parents already fill covers the bedtime job today.
Second-kid profiles — two siblings sharing one device, each with their own contacts and library; parked because profile switching taxes the one-button simplicity that is the product, and unclaiming and re-claiming a device already makes hand-me-downs ordinary.
Kid-to-kid yoyopod notes across households — voice notes between friends’ devices, not just within the family; parked because it requires two sets of parents to approve each other’s kids, and that consent flow deserves to be designed slowly and well, not bolted on.

Ideas leave this list in one of two directions: unparked into real design work once the pillars are solid, or moved down into the rejected list when closer inspection finds a principle they cannot pass.

Explicitly rejected

These are not pending features. They are decisions, and writing them here keeps them decided.

yoyopod is not a smartphone replacement — and it will not become one a single reasonable feature at a time. Drift is how every simple device dies, so the wall is explicit: no camera, no browser, no app store. Ever. Those three absences are permanent design decisions, not gaps waiting for a bolder roadmap.

We will also never market it as AI for kids, a new communication platform, a smart wearable, or an educational device — each label dilutes the sharpest truth, that this is the first device before a smartphone. And it is not a toy, not screen-first, and never engagement-optimized: no streaks, no badges, no notifications engineered to be missed. Push-to-talk only, forever — no wake word, no always-listening mode — is the same kind of commitment: permanent, not provisional.

The full argued stance lives at what we are not. Nothing enters this parking lot, and nothing ever leaves it, in a way that contradicts that page.

Still being decided

What makes the V1 pillars “solid”? Measurable bars — real households, weeks of daily use, support-load thresholds — that must be met before anything here moves forward, so “solid” is a checklist and not a mood.
Do parked ideas need to run on today’s hardware? Whether an idea must work on the current board to earn a place here, or whether hardware-dependent ideas may wait, flagged as gated on a future revision.
How do family requests feed this list? Parents will ask for features; whether those requests formally feed this page — and how to say no in the product’s voice when they fail the test — is still open.