What the local prototype is exploring.
The current development work connects recipes, weekly meals, groceries, and pantry records. These are prototype workflows, not a claim that a released app is ready to use.
Recipes and imports
Recipe entry and editable review drafts for URL and photo imports.
Weekly meal planning
Meal planning with servings, ingredient snapshots, and planned leftovers.
Grocery lists
Meal ingredients and manually added essentials, organized by store and department.
Pantry tracking
Pantry notes and quantities connected to shopping and cooking actions.
What is not available yet.
- Household sync. Shared household use and separate Google sign-in are not connected. Do not expect another phone to see the prototype’s data.
- A public download. There is no public app-store release or download offered on this website.
- A launch date or pricing. Neither has been announced.
The website’s sample week is an illustration. It does not create an account, save recipes, generate your grocery list, or sync your household.
What comes before a public release.
Shared household access needs secure account and invitation flows, reliable synchronization, and careful testing of simultaneous changes. That work is a priority.
The app also needs further device, accessibility, data-recovery, and security testing. Product scope and implementation may change as testing continues.
For something practical right now, the pantry-first planning guide works with a notebook or a list on your phone.
About this website.
This website introduces Shelf2Spoon and provides a meal-planning guide. It does not accept account registrations or collect email signups, and it does not contain advertising, analytics scripts, or embedded third-party widgets.
The sample preview only changes which example is displayed in your browser. It does not store or transmit your input. No personal recipe, pantry, or household data is requested here.
The hosting provider may process ordinary connection information, such as an IP address, to serve and protect the website. Linked websites have their own data practices.
This describes the website as built, not a future app privacy policy. App data practices will need to be documented before public release.