Why? It doesn't have to be the idea itself. You can ask questions to check whether it is a problem first as opposed to talking about your solution. What if they're not aware it's a problem, or don't care about it? It's harder to sell a solution to a problem to someone who is not aware of the problem or does not care about the problem than it is to someone who's well aware, who cares about it, and who's tried to solve it but failed.
>and because my app would require some kind of technical infrastructure i don't wanna start talking with local restaurants.
Why?
>i feel like i can convince the big boys and the locals would follow them.
Feel? Wouldn't having actual conversations and learning things that are invisible to you right now beat that and shed light on many things?
So? You'll talk with many people you didn't personally know. Case in point, we're having this conversation.
>2. i want restaurants to keep their menus and kinda "host" their menus themselves. and i won't be providing any customer service or something like that. because of that, i want corporate restaurants have tech infrastructure.
I'm sure you have reasons that lead you to this, and I'm sure you'll learn many things talking with people in the field.
>3. my only concern is about the product
So many built the best product people never used.
Please get out there and talk with people in a way they'll tell you about their problems and what they've done to solve them or not.
What would you say, if you probe a little bit and get a slight understanding of problems, and then, learn how to code just that. Little by little, you learn and stay motivated because you're converging towards something real.
However, if you are completely indifferent to the outcome, then by all means, go ahead; programming is fun for its own sake. It's just that the premise of this conversation was misleading.