I don't think that's the interesting point. The problem is that the focus on design means that developers spend too much effort on design and not enough on quality. We build tools to make design easier rather than making quality easier for developers, result in a market full of worse software that only appears better on first impression.
In some sense it's an evolutionary necessity: When people make choices based on eye candy, suppliers who provide better eye candy make more sales, and the rational supplier then spends more effort making better eye candy and some of that effort comes out of what could have made a better product in other ways.
But in theory, if there was a way to throw a wrench into that dynamic -- a better, faster, easier way for users to evaluate overall quality rather than relying on superficial aspects of design quality -- then we should welcome it (or work to create it, if you're so inclined).