Again, it depends on why you are designing something. If your goal is to just stroke your ego then you probably aren't going to care about the end user.
Whenever I see "should" in a sentence I think: why is this not how things are? What are the incentives? In this case: who is the person deciding what gets built? What are the consequences for being over budget? (Calatrava I am looking at you).
This is about expectations. Good architecture serves many users. Good films serve many viewers. Good software ...
You get the point. And it is always better if you can serve two target audiences at once instead of one – IF you can do it without compromising.
But some software doesn't want or even need to serve all users. Take vim for example. For most people it would be a horrible experience to use it and they could criticise it for a ton of things. But what value is there in this cricism as they don't understand how vim is intended to be used? Their cirticism comes from a true place, but it still isn't worth a lot, because if you followed it to the end you would end up with something like notepad.exe or MS Word and loosing everything that makes vim special and interesting.
So if anything, what I say here is: good criticism is critcicism by people who see the same thing in your thing as you do, as their vision likely aligns with yours. If you are painting impressionist pictures for example, the criticism "it could look more photorealistic" by some guy is utterly useless, while the criticism "I think you should rely less on simple complementary color combinations" by someone who understands impressionism might be really helpful. The photorealism guy just tells you that there are people looking for this out there, but as you already know and/or actively decided against it, there is no use in this.
Meanwhile, anything on the internet you're reading/watching/listening to is by your choice.