The Default Setting Problem in Kids' Tech | myFirst
The default setting problem
What your kid’s first device
assumes about them
Before anyone clicks a button, the default settings have already made an assumption about your child. The best safety feature is the one you never had to switch on.
Day oneWhat happens when your kid opens something for the first time
You hand your kid a new device. Before anyone clicks a button, the default settings have already made an assumption about your child. They assumed she’s safe. Or they assumed she needs to be protected.
In 2024, the OECD published Towards Digital Safety by Design for Children, built on one principle: the default configuration must be the safest available option. Because the vast majority of users never change their defaults, and kids are overrepresented in the group who couldn’t, even if they wanted to.
In practice, the default is the product.
The retrofitWhy bolted-on safety falls short
Roblox announced over 100 safety measures in 2026. Trusted Friends. Age-tiered chat. Parent-linked accounts. Not bad ideas. But critics have pointed out something uncomfortable: safety education and retroactive fixes can’t address fundamental design choices.
Reporting around the lawsuits suggests the company could have implemented age verification years earlier and chose not to. Call it age as an afterthought: design for adults first, then bolt children’s safety on once the pressure mounts. It’s a familiar pattern across children’s tech, and it points to an uncomfortable conclusion: for most platforms, safety simply isn’t the default.
The frameworkWhat “safe by default” actually looks like
The OECD framework isn’t abstract. Three of its components reveal the gap between “safe by design” and “safe by update.”
Notice the pattern. None of these are features you add. They’re decisions about what doesn’t exist. Safe by default doesn’t ask “what can you do?” It asks what the product refuses to allow.
The whole lineWhen every product answers the same way
That question becomes visible across an entire product line when a company builds around the same default assumption: what does this device assume about my kid the day she first picks it up?
One question, asked consistently. Each product answers that she needs the dangerous thing to simply not be there.
The principleThe architecture of intention
The OECD report says it plainly: most users never change defaults, and children disproportionately can’t. So the default isn’t the starting point of the experience. It is the experience.
Roblox’s 132 million daily users signed up before these safety measures existed. Their default was open. The 100-plus updates came later, and they matter, but they can’t retroactively change the assumption baked into every user’s first impression.
A product that’s safe by default makes a different assumption from the start. Not “we’ve provided a safety option,” but “the unsafe option doesn’t exist here.” No toggle to forget. No update to download. The protection was there before the child was.
Roblox’s updates are good news. So are Meta’s teen accounts, YouTube’s supervised experience, Discord’s Family Center. The industry is learning.
But there’s a quiet question underneath: what happened to the kids who used the “before” version? The safety features came eventually. But “eventually” is a long time when you’re nine.
My daughter won’t be a first-generation test case for a product still figuring out how to be safe. Not because I don’t trust her. Because she’s seven. She shouldn’t have to be her own security system.
The best safety feature isn’t the most advanced one. It’s the one you never had to download.
