Trivet
Recipe box, weekly meal planner and grocery list for one household.
Add a recipe from a link, a PDF, a photograph of a printed or handwritten
card, pasted text, or screenshots of a caption shared from your phone, plan a
dinner for each night from your library, and take the resulting shopping list
to the shop.
Live at trivetbox.com, and on iPhone in a family beta
(TestFlight, build 5). Releases are tagged: v2.0.0 is the current one, with
its notes on GitHub, and each TestFlight build gets an app-<version>-<build>
tag (app-1.0-5) so a tester's report can be traced to the code they ran.
The case study covers why it works the way it does: the
problem, the decisions, what was cut, and what comes next.
Demo video
https://github.com/user-attachments/assets/f4008d4c-4334-4b36-83d7-cc69ad15a5a2
What it looks like
The library, newest dish given the hero and the rest in a grid. Collections are
a curated way in; everything else lives behind Filters.
A recipe, with everything the card printed: timings, resting, oven temperature,
equipment, and what the household thought of it.
The week, and the list it produces. Ingredients roll up across the meals
planned, grouped by aisle, with the dish each line came from underneath it.
Add a recipe from a link to one online, a PDF, or a photograph of a card.
Screenshots are of a seeded demo library, so no dish photos are attached - the
striped placeholders are what the app draws when a recipe has none. They are
taken from npm run seed:demo, so retaking them is a command rather than an
afternoon:
npm run browse:seed # once, with the app running
npm run seed:demo
npm run browse -- /recipes --shot=docs/screenshots/recipes.png
npm run browse -- /recipes/zuni-chicken-with-bread-salad-03a14891 --shot=docs/screenshots/recipe.png
npm run browse -- /plan --shot=docs/screenshots/planner.png
npm run browse -- /upload --shot=docs/screenshots/upload.png
npm run browse -- /pantry --shot=docs/screenshots/pantry.png
npm run browse -- /household --shot=docs/screenshots/household.png
The recipe's address is stable across reseeds: seed:demo derives each
publicId from a hash of the title rather than at random, so the hero keeps
the same URL and this command does not need editing every time.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
