vs target 2,340
Pantensa prototype: logging a meal and closing the day
This is a prototype, not the app. Pantensa has not launched yet: there is no account behind this screen, the numbers are made up, and nothing you change here is saved.
The day screen is where a meal becomes numbers. You add what you ate from your own products and recipes, correct it when the details turn out different from the plan, and close the day against your own targets.
What this prototype shows
- Adding a meal to breakfast, lunch or dinner — searching your own products and recipes, not a stranger’s database.
- Cooking a recipe with changes: the smoothie says berries, you had raspberries, and the day takes the raspberries.
- Closing the day, which freezes what was eaten, and reading it back against calories, protein, fat and carbs.
vs target 2,340
A saved set of lines — “my usual breakfast”, “training day” — that drops into the list in one tap and is then edited line by line, like any other set.
A separate table with its own CRUD holds the definition; applying it is a
front-end expansion into those same lines (decision 2026-08-04).
So there will be no fifth line type, meal_plans does not change, and
adding rides the same batch request. A line does not remember that it came from a
template — editing the template later does not rewrite days already added.
Creating and editing templates will live in the Kitchen, where a “Templates” tab already exists. Here on “Today” templates are only consumed — which is why this tab is deliberately empty until the feature reaches planning.
Actual amounts go into history as fact. After that we ask separately whether to update the recipe itself.
Clears the “done” mark from every line — and unfreezes the nutrients. The day will be counted against current product data again, so the numbers may change. The cooking history and the stock deductions stay.