Homeboard

Our household needed one shared source of truth — calendar, to-dos, meal planning, countdowns — that worked equally well glanced at from a tablet on the fridge and updated quickly from a phone. Most "family dashboard" apps I looked at were either too rigid or wanted a subscription for features we'd use once a week.

• Split one app into purpose-built surfaces from a single index.html — a landscape wall-tablet display that auto-rotates through shared info, and a portrait phone admin for quick updates — each reading and writing the same Supabase project
• Built self-serve household signup with invite codes and a 4-character display-pairing flow, both backed by Supabase Edge Functions rather than direct client writes, so a new tablet can join a household without its own login
• Layered in features as real household needs came up — meal planning with a saved-name typeahead, live game-night scorecards, countdowns, and an admin-only wedding RSVP flow — all on one Supabase project and one to-do/calendar core
• Integrated with a completely separate wedding-site repo's rsvps table by only ever adding nullable, additive columns — never touching the columns that repo owns — so two independently-deployed apps could safely share one table

It runs on a tablet on our fridge every day and is genuinely the thing we both check for what's for dinner and what's coming up this week. The cross-repo RSVP integration was the best lesson: respecting another system's ownership boundary with additive-only columns meant two apps could share data safely without ever coordinating a deploy.