For hobby projects, I agree with you whole-heartedly.
The thing is, things are products. But the answer isn’t “all hackers are wrong, you’re dumb for not involving me early on.” Rather, the answer is ‘chill, you’ve got this.’
We don’t need a product placement meeting before we type git -m commit “First commit” and if we did, the bast majority of cool things would never have been built. Sometimes we just build because that’s what builders do.
When I am working for someone who is paying me, though, I am only building for one reason; to deliver value to my employer. That is the entire reason I am being paid. I build for other reasons at other times.
I really hate working with other developers who think like you do. It is so hard to work with people who care more about the code itself than what it is for. We aren’t working for the same goal, and sometimes the beautiful code actually makes it harder to accomplish our actual goal.
This is just a single data point, but for a view "from the other side", my honest and immediate answer to this question is: "I don't care".
When writing programs, my concern has never been "to deliver a high-impact product". In fact, I find this language very annoying; and saying that my program is a "product" feels like a very offensive insult. The goal is never to deliver a product, much less a high impact product. The goal is always to solve a problem that I have, regardless of whether any other person on earth has the same problem. Now, I may have been given that problem because it was deemed useful to other people, but during the actual act of programming I prefer to make an abstraction of that and focus only on the problem itself.
EDIT: I appreciate that there are managers and such that keep proposing meaningful problems. I also like to find problems myself, and sometimes I appreciate when (rarely) they turn out to be shared with others, who in turn are happy that I solved them. But this is always a happy secondary effect, never the main goal.