family OS

You read the startup blog post. The phrase is "the operating system for your family." There's a clean diagram. Shared calendar, shared tasks, shared inbox, shared memory. Everyone in the household, on the same layer. You recognize the language — it's how you've been describing the problem to your partner for years. You also know, before you finish the demo, that it isn't going to work, because the everyone part is the part that's broken.

There's a category name for the framing. People call it family OS — short for family operating system — a metaphor that treats the household like software. Shared inputs, shared state, shared outputs. The framing is genuinely useful as a strategy claim: yes, families need one source of truth for the week. Yes, the coordination problem is real. Yes, software can help.

You're not bad at "getting everyone on the system." The metaphor's limit is the assumption underneath it — that both partners are equally engaged users with equal stake in the system's upkeep. The default parent reality says they're not. Family OS works on a slide. In a kitchen, it ends up used by the parent who would have run the calendar in their head anyway, while the rest of the household keeps asking that parent the same questions.

Family OS sounds clean on a slide. mellie's built around the parent who's already doing the work — not the household-as-software. Smaller, warmer, on your side of the kitchen. The system that doesn't need everyone to log in for it to help.