Rahul hit the nail on the head on the recipe finder app I was thinking about.
- The biggest blocker for is that I just don't care enough (or I'm too lazy) to try out new recipes. I just default to things I've made before, a ready-made meal, or Chipotle.
The YC founders talk about how "discovery" (music/band/concert/event/apps/food/restaurant) apps a tarpit idea -- everyone thinks of these ideas, realizes its fundamentally broken, but no one can fix it
The reason -- people default to the most common option or things that are popular. And I noticed that with this app as well
My new suggestion is a recipe tracker instead. Paste a link and it organizes/sorts it
Pros
Cons
I don't anyone who would actually want to use and not use it because I'm asking/making
There's a book called "The Mom Test" where the author teaches you how to talk to people without biasing them before building our your idea. I highly recommend reading that book to find out how to measure demand for an app.
If this helps at all, here's how I plan out my cooking:
I will usually use Sunday to plan out what meals I want to cook for the week. I usually cook 4 recipes total, two for lunch, and two for dinner, but I cook enough where each recipe lasts 3 meals. For the recipe generation step, I usually will see what's on sale at a grocery market or I'll check my fridge to see what ingredients I have. I'll usually look for a new recipe or see what I've cooked in the past.
It sounds like this is where your app might step in. Do you know what your app would offer me over looking through my notes to find recipes I've cooked in the past?
How are people tracking recipes today? I don't do this today, but I imagine Pinterest or some notes doc? Is there a particular set of users who are under-served with existing tools?
This may not be entirely relevant for you since you're not trying to turn this into a big VC-backed company, but one of the traits of the best startup ideas is that they've discovered a unique insight about some users. The product is a natural consequence of that insight.
You're not trying to create the next Airbnb, you are just trying to get something with 1,000 users so the project stands out among the 98% of engineers whose projects have 0 users. I personally think a slick recipe app could achieve that. But will it become a billion dollar company? Definitely not.
The problem with having some sort of recipe tracker is that you go from just R in CRUD with the recipe discovery app to the full CRUD lifecycle. That's a lot more work, both for you and the user. End-users are lazy, so unless your interface is very, very good, they just won't put in the data to make your app useful for them.