Home cooks lose and struggle to manage recipes across sources
Home cooks collect recipes from websites, social posts, files, and printed cookbooks, then struggle to import, search, revisit, share, and preserve their own iterations. The evidence shows workarounds such as writing scraping scripts, keeping separate copies, and copying old posts into a Google Doc; cluttered search results also make trustworthy recipes harder to find. A personal recipe library could improve capture and organization, but it cannot by itself certify a recipe or reliably identify AI-generated imagery.
For home cooks maintaining personal or household recipe collections. Mentioned from Dec 2019 to Jun 2026 on Bluesky, GitHub and Hacker News.
11 different people described this problem in 9 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 4.9/10
- Frequency
- 9.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Consumers
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
I've been writing rudimentary Python scripts to scrape online recipe websites for my hobby cooking purposes, and I wish there was some general software that could do this more simply
I would like to share my recipe for example with my wife (she has an account in our nextcloud). We don't want to have all the recipe twice
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 9 more quotes from people who have this problem
- Current workarounds, existing solutions and risks