The working app · 4:20 walkthrough
A kitchen, in rhythm.
From the food you have to a meal you can make. Watch the pantry, planning, shopping, and cooking loop.
Follow along at your pace
The full walkthrough.
Every spoken word, in scene order. Times indicate the beginning of each scene.
Good meals start with what is here
PantryLoop helps a home cook plan meals around the food already in the kitchen. It connects manually maintained pantry quantities, editable recipes, and a meal plan in one browser workspace. The opening kitchen is labelled as a sample. Its seasonal produce artwork is a generated illustration, not a photograph of actual inventory. This narrated interface walkthrough uses real app screenshots and synthetic narration to explain the planning loop.
Record the food you actually have
Each pantry lot has a name, quantity, unit, storage location, and personal use before target. Separate lots can represent food purchased at different times. These targets help organize attention, but they do not establish food safety. The user remains responsible for checking the actual ingredient. Quantities can use grams, kilograms, milliliters, liters, pieces, or cups. Matching units stay explicit, so a pantry entry is more useful than a simple checkbox.
Plan a meal with the right quantities
A meal combines a recipe, a date, and a serving count. Its ingredient requirements scale with the selected servings. The allocation engine processes uncooked meals in date order, and draws from matching pantry lots in target date order. That means the same ingredient quantity is not promised to two meals at once. A recipe that was possible in isolation can correctly show a shortfall after another meal reserves the available stock.
Buy the shortfall, not the whole recipe
The shopping list collects shortfalls across the plan. In this captured example, it lists one hundred sixty grams of carrot and ten grams of ginger, matching the meal editor. Compatible units convert automatically, including grams and kilograms, or milliliters and liters. Cups and pieces remain separate. Checking an item marks the list only. The plus action opens an entry for the actual purchased quantity. CSV export makes this calculated list portable.
Record cooking as a real stock change
The captured meal plan now marks the sample chickpea bowl as cooked. Its ingredients have been deducted from the pantry, while the second meal still shows its missing ingredients. This is a saved planning record, not evidence that a real person cooked the meal.
Close the loop when a meal is cooked
When a fully supplied meal is marked cooked, PantryLoop deducts its reserved ingredients and records the quantities used. A meal with missing ingredients cannot be logged as if it were ready. The cooking journal shows the resulting record, with an undo action that restores the exact quantities. Repeating the cooked action does not deduct them a second time. This completes the connection between planning a meal and maintaining an honest inventory afterward.
Let the pantry guide the choice
The recipe view compares ingredient needs with inventory that has not already been reserved by planned meals. Recipes with ingredients near their personal targets are surfaced first, followed by ingredient coverage. A servings selector changes the quantities being considered. Search and an everything available filter help narrow the list. This matching is deterministic, using the saved recipes and quantities; it is not presented as an artificial intelligence recommendation or dietary advice.
Keep control of the kitchen data
The kitchen lives in local browser storage. Settings provide a JSON export for backup or moving to another device. An imported kitchen is validated and previewed before replacement, with a reminder to preserve the current kitchen first. A clean start is also available for people who prefer to enter their own inventory and recipes. There is no cloud synchronization, so exporting a backup is the practical way to protect the work.
A practical habit, without invented impact
PantryLoop follows the practical idea of checking existing food and planning meals before shopping. Its records describe quantities entered, reserved, and logged; they do not prove money saved, emissions avoided, or food waste prevented. The app was developed with AI assistance, while its planning logic is deterministic. The finished loop is straightforward: maintain the pantry, choose a recipe, plan servings, buy only the shortfall, and update the kitchen when cooking is done.