Kitchen PWA
WellStockd
Live product
WellStockd answers the daily kitchen questions from the fridge door: what’s in the fridge, what can I make right now, what should I cook this week, and what do I need to buy. It runs fullscreen as a PWA on a fridge-mounted tablet — and the same account works from a phone or PC, because nobody wants to type a recipe on a fridge.
The core is bookkeeping nobody wants to do by hand: cooking a recipe atomically subtracts its ingredients from the inventory, anything that runs out lands on the shopping list, and the weekly meal plan feeds the list too. Those flows run as Postgres functions, so the numbers never drift.
Inventory-aware recipes
"What can I make" is computed against the real inventory — a can-make-now list plus an "almost" list where the one or two missing ingredients tap straight onto the shopping list. Every ingredient keeps one canonical unit, so cooking subtracts exact amounts with no conversion guesswork.
Built for the fridge door
A step-by-step cooking mode with large text, built-in timers, and a screen wake lock — advance by tap or swipe. When the tablet idles, the app falls back to a dimmed dashboard of today’s meals and the shopping list that brightens on touch.
Self-maintaining shopping list
The list fills itself from three directions: items that hit zero, items used up by cooking, and the weekly planner. A one-tap Walmart hand-off fills a cart when affiliate keys are configured — and degrades gracefully to a shareable text list plus per-item search links when they aren’t.
Households, reviews & a real catalog
A household model shares each member’s recipes with the family read-only (RLS policies enumerate and preserve every prior grant), recipes carry 1–5-star reviews, and a family-favorites view surfaces what everyone actually likes. A photographed recipe catalog seeds the library so the app is useful on day one.
One Supabase project, many apps
WellStockd shares a single Supabase project with several other small apps, isolated by Postgres schema. Supabase Auth keeps one identity store per project, so the app namespaces sign-in emails per app (you@x.com → you+wellstockd@x.com) — every app gets its own account and password while real mail still reaches the same inbox.
Start a project
Want something like this?
Tell me what you're trying to build and I'll come back with a clear, practical plan.