How does Kubrio design its apps?
Every Kubrio app is built the same way. We research the science behind the subject first — the actual papers, everything known about how kids learn it. Then we prototype, make sure it's safe, launch quickly, and improve continuously with feedback from kids — some of whom become Quality Guardians and help us build.
Every app in the studio, from Sketchling to Stocks, goes through the same process. We think parents should know what that process is, because it explains both why the apps work and why the studio keeps changing under your kid's feet — on purpose.
Step 1 — Research the science
Before anything gets built, we do extensive research on the science behind the subject. Not a skim: we go through the research papers and pull together what is actually known — how kids develop the skill, at what ages, what helps, what quietly backfires. For animation, that meant the research on drawing by hand, storyboarding, and visual memory. For investing, the research on how kids form ideas about money and risk.
The research decides the design. If the science says the drawing must happen on paper for the skill to build, the app gets built around paper — even when a screen would be easier to ship.
Step 2 — Prototype, then make sure it's safe
We build a working prototype quickly and hold it to one gate before any kid touches it: safety. The same rules that govern everything else at Kubrio apply from the first version — every kid–AI message checked by a second AI, no strangers, nothing collected that isn't needed. The full picture is in safety and data.
Step 3 — Launch fast and listen to kids
Then we launch — soon, not someday. A prototype in front of real kids teaches us more in a week than a design document teaches us in a quarter. We watch what kids actually do with it, where they light up, where they stall, and what they build that we never expected.
Step 4 — Kids help us build: Quality Guardians
The feedback loop has a name, and your kid can be part of it. Kids can become Quality Guardians: when they hit a glitch or something that feels off, they report it right from the studio. When a report is confirmed, they earn Quality Guardian tiers — real recognition for genuinely helping build the product.
This is quietly one of our favorite things in Kubrio. A kid who reports a bug, sees it confirmed, and watches the fix ship has just experienced the core loop of product management from the inside: notice, describe precisely, verify, improve. That's not a lesson about how software gets made — it's the real thing, with their name on the contribution.
Step 5 — Always improve
No app is ever finished. The apps your kid uses today are running versions of this loop — research feeding design, kids feeding feedback, improvements shipping continuously. It's the same standard we hold the kids to in their own projects: make it real, show it, make it better. New apps join the studio the same way — see what new apps are coming.
Frequently asked questions
How does my kid become a Quality Guardian?
By reporting bugs from inside the studio when they find them. Confirmed reports earn Quality Guardian tiers. There's nothing to sign up for — the first confirmed report starts it.
Do kids' ideas actually change the apps?
Yes. Prototypes exist to be changed by what kids do with them, and confirmed bug reports ship as fixes. Founding families can also bring ideas straight to the founder — see [getting set up](/docs/getting-set-up).
Why do apps sometimes change under my kid's feet?
Because the loop never stops. We'd rather your kid use an app that improves every month than a polished one frozen for a year. Claire and the studio carry their work forward through changes.
Is a brand-new app as safe as an older one?
Yes — safety is the gate a prototype must pass before launch, not something added later. The second-AI check and the no-strangers rule apply from version one.