Mission & Story
Why yoyopod exists and who is building it.
The gap before the smartphone
Section titled “The gap before the smartphone”Kids ages 7–14 want independence before parents are ready to hand over a smartphone. yoyopod is built for exactly that gap — a parent-managed first independent device that gives kids focused independence (communication, music, mobility) and gives parents peace of mind through reliable calling and live-ish location, without a smartphone’s distraction, complexity, and screen addiction.
The positioning line, verbatim:
Safer independence for kids. Peace of mind for parents. Before the smartphone.
“The first device before a smartphone” names a category, not a competitor. The public story is built around three parent questions, in this order: Can I reach my child? · Can they reach me? · Can I see where they are? yoyopod is built around those questions first.
Our answer
Section titled “Our answer”| Attribute | Value |
|---|---|
| Buyer | parents |
| User | kids ages 7–14 |
| Product type | parent-managed connected companion device |
| Form factor | walkie-talkie-like, tiny screen, minimal input |
Four V1 pillars carry the promise:
- Whitelist calls and voice messages — approved contacts only.
- Live-ish location — visibility when it matters. (The hedge is deliberate: it is not marketed as real-time tracking.)
- Music and audio — an everyday audio companion.
- A parent mobile app — contacts, settings, and device controls stay with the parent.
The emotional promise splits cleanly: for the kid, independence — a device that feels grown-up and is genuinely theirs; for the parent, safety and peace of mind. Two trust anchors carry it: reliable reachability and trustworthy location. Everything else is secondary — including everything the answer refuses to be (What yoyopod Is Not).
For kids, yoyopod feels like freedom. For parents, it feels like reassurance. For both, it’s a better step before the smartphone years.
Who we are
Section titled “Who we are”Software-engineer fathers in Stuttgart, Germany, building the device we wanted for our own kids — which means the product gets tested on its actual users at our own dinner tables. The engineering choices trace straight back to the mission: one button and a small calm screen because simplicity is the product, whitelisted calling and voice notes because safe communication is pillar one, cellular + GPS because reachability and location are the trust anchors.
The work happens in the open at
github.com/attmous/yoyopod; the
as-built engineering docs live in the main docs site (docsite/website/ in the
repository). The rules that keep us honest are written down as
Product Principles.