Case Study

Mealio

An AI kitchen assistant concept — plans a household's dinners for the week around what's already in the kitchen, and turns the plan into one grocery list.

View Prototype Back to Projects
Status
Concept · Pre-Launch
Role
Solo Builder — Product Concept, UX Prototype
Stack
Interactive Prototype (backend planned: Supabase · Vercel)
The Problem

"What's for dinner" is a decision made hundreds of times a year

Deciding what to cook every night is a small decision repeated constantly, and it's the one that quietly drives the most wasted groceries and last-minute takeout — not because people don't want to cook well, but because planning ahead takes more effort than most evenings allow.

The Goal

Remove the decision, not just organize it

The goal is a full week of dinners planned around a household's taste, the season, and what's already in the pantry — reconciled automatically into a single grocery list — with a guided, step-by-step "cook mode" that sequences timers across multiple dishes at once.

Where It Stands

A locked design, proven through a full clickable prototype — no backend yet

Mealio exists today as an interactive HTML/CSS/JS prototype covering Home, Weekly Menu, Recipe Detail, Market List, and Cook Mode, plus a marketing landing page with a waitlist. It's honestly a prototype, not a live product yet: there's no backend, and no tech stack decision has been made for one. When it needs a backend, the plan is to default to the same Supabase + Vercel pattern already proven twice over in Profity and Kaspit, instead of re-evaluating options from scratch.

Interactive HTML/CSS/JS Prototype Planned: Supabase Planned: Vercel
Result

Concept validated, product not yet live

The design direction is locked and validated through a full clickable prototype. It isn't a working product yet — the next step is the backend decision above, then building the real app behind the prototype rather than shipping the prototype itself.