A Meal Planner That Spits Out a Shopping List
Meal planning is one of those things people try, abandon, try again, and quietly give up on. The fail patterns are predictable:
- Week 1: enthusiastic. Detailed plan, color-coded, all seven dinners assigned.
- Week 2: shorter. Couple of slots are "leftovers."
- Week 3: gone. Back to "what's in the fridge" mode at 6 PM.
The friction isn't planning itself — it's everything around it. Building the plan takes 20 minutes. Then you have to extract a shopping list. Then you go to the store and remember that you forgot two things. Then on Wednesday a child-related crisis means Tuesday's planned chicken thighs become Friday's emergency repeat.
The tooling can help with two of those: making the plan fast to build, and making the shopping list fall out automatically.
The drag-free grid
A meal planner that needs you to drag ingredients around is hostile to anyone using it on a phone, on a laptop trackpad, or with two hands full of toddler. A grid where you type meal names directly into cells is fast.
The grid we built has 7 days × 4 slots (breakfast, lunch, dinner, snack). Click any cell, type the meal name. That's the plan. Done in under 2 minutes for the typical week.
The ingredients-per-meal trick
Each meal cell can also store an ingredient list (one ingredient per line, free-text). The shopping list view then aggregates every line across the whole week, dedupes by line text, and sorts alphabetically. Walk into the grocery store with that.
Why this matters: without it, you have to re-derive the shopping list from the plan. That's a 15-minute task that isn't fun, and it's the friction that kills meal planning by week 3. Eliminating it changes the user behavior from "fill out plan, then export shopping list" to "type ingredients as you plan, shopping list happens automatically."
Multi-plan support
Most weeks aren't from scratch. The plan that worked last month works again. The kids' favorites plan covers a lot of weeks. The "low-effort week" plan is the one for sick weeks.
A meal planner that lets you save and switch between multiple plans, plus duplicate one to start from, lets you build a small library that handles 80% of weeks without re-typing.
The "duplicate plan" button is the unsexy feature that makes weekly meal planning sustainable. Copy last week, change the two things that aren't repeating, save. Two minutes, fed for seven days.
What to skip from a "real" recipe app
A meal planner doesn't need to be a recipe app. It doesn't need to know that 2 cups of milk is 480 mL. It doesn't need to convert between units. It doesn't need a database of recipes. Those are different problems.
What a meal planner does need: a place to put what you're cooking when, and a clean way to get the shopping list out of it. Less is more.
Print for the fridge
A printed weekly plan stuck on the fridge is an artifact that gets used. It tells anyone walking by what's for dinner Wednesday. It survives the kid asking for the third time. It doesn't need a phone.
Our planner has a print stylesheet that hides editor chrome and outputs the grid in a format that fits on letter-sized paper. Print Sunday night, look at it all week.
Skip the spreadsheet
The Weekly Meal Planner does all of this. 7-day grid × 4 meal slots, click a cell to add ingredients, switch tabs to see the deduped shopping list with check-off. Multi-plan support, duplicate-plan button, print stylesheet. All on-device — no upload, no account.
The short version
Meal planning fails at the friction points around the planning itself, not the planning itself. A drag-free grid, ingredients flowing into an automatic shopping list, multi-plan support, and a print button — that's enough infrastructure to make the habit stick past week 3.