A meal planner has more state than its calendar suggests

Moving a dinner from Tuesday to Thursday looks like a small UI action. The interesting question is what moves with it: the serving count, ingredient choices, recipe instructions and shopping quantities.

I looked through MealMuse, a free dinner-planning web app, with that question in mind. These are observations about the visible workflow, not its source code.

Actual interface screenshot. Food artwork is AI-generated illustration.

A recipe is not the same thing as a planned dinner

A recipe describes a dish. A planned dinner also needs a date, a serving count and any supported ingredient choices. MealMuse offers household portions of one, two, four or six, along with per-dinner controls. Moving the dinner should preserve those choices rather than quietly reset them.

That distinction is a useful starting point for a data model. The calendar item is an instance of a recipe, not just a recipe ID in a date column.

The ready-made two-person plan is a starting point, not a locked schedule.

A substitution reaches beyond the ingredients panel

The site supports selected ingredient alternatives. Its homepage gives paneer-to-tofu as an example: the method and grocery list follow the chosen alternative. That is more meaningful than replacing one word in an ingredient label.

A useful test case would be: choose an alternative, change the portions, move the dinner, then inspect the grocery list and the cooking instructions. Do they still describe the same dinner? That is a proposed check, not a claim that I inspected the implementation.

Grocery totals are not supermarket pack sizes

The two-person plan explicitly says its list contains recipe quantities, not automatically rounded shopping packages. That is an important boundary. A recipe requiring part of a package does not mean the shop sells that exact amount.

Keeping this visible is better than letting a precise-looking list imply a promise about waste or cost that it cannot keep.

No account changes the persistence contract

MealMuse keeps plans in the current browser. It does not currently sync them between devices. Clearing browser data can remove access to a plan, so copying the list or downloading a PDF matters.

For a browser-local tool, I would treat exports and clear storage explanations as part of the main workflow. “No signup” is useful only if people also understand where their work lives.

You can explore the workflow at usemealmuse.com. It is currently a beta; the site says its recipes and timings still need hands-on kitchen testing. The interface is available to try, but it should not be presented as a collection of kitchen-tested recipes.