Today's Magnet

My sister-in-law manages family coordination across two households from a divorce — sports schedules, birthday parties, cancellations, updates — all of it spread across multiple group chats, with the same information going to different people in different threads. My husband and I sit at the overlap of both family groups, which means we're always the awkward relay station in the middle.

The problem wasn't that people weren't communicating. It was that the tools weren't built for how families actually work. Group chats are flat. Family life is layered. Some things are for everyone, some things are only for one side, and some things are nobody's business except the parents.

I kept thinking: there should be a place where the right information reaches the right people — without the two sides of the family ever having to cross unless they choose to. That's what Today's Magnet is. Not another group chat. A family fridge, where you put things that matter, and everyone who needs to see them can.

Today's Magnet is a private family coordination platform built around the concept of a household as a "fridge" — a shared space where families post events, announcements, polls, and wish lists, with privacy controlled through family circles that determine who sees what.

I started the build in Base44, a no-code platform I'd used for earlier projects. I hit a wall fast. Base44's built-in auth couldn't handle the security complexity Today's Magnet actually requires. Households need true row-level security. Circles need scoped access. A managed members model — where kids or elderly family members are added without their own accounts — needs a permission architecture that no-code auth simply can't provide cleanly.

So I made a deliberate decision: rebuild from scratch on an owned stack. I migrated to Next.js, Supabase (with full RLS policies), Vercel for deployment, and Resend for transactional email. I used Codex to accelerate the build. The migration wasn't just a technical upgrade — it was the moment I stopped building inside someone else's constraints and started building to my own spec.

A look at the real product — the family fridge in action, from the events feed to the circle controls that keep each post private to the right people.

The biggest lesson was about the gap between security complexity and user experience simplicity. Getting row-level security right in Supabase — scoping data correctly across households, circles, managed members, and roles — was the hardest technical problem I've worked on as a builder. The policies are intricate. But the end user should never feel any of that. They just see their fridge.

Holding both of those things at once — deep backend complexity and surface-level calm — is the real design challenge. It's not enough to build something secure. It has to feel effortless to someone posting a soccer schedule at 7am before school drop-off.

I also learned what it means to outgrow a tool deliberately. Leaving Base44 mid-build wasn't a failure — it was the right call at the right moment. Knowing when a constraint is a limitation versus a forcing function is a skill I didn't have before this project. Now I do.

And building for a real, specific person — my sister-in-law — kept me honest. Every feature decision had a test: would this actually help her? That's a better filter than any product framework.

Today's Magnet is currently in private testing with a demo household. The roadmap from here: