So I guess this dark pattern is now being elevated to a design best practice...
So I guess this dark pattern is now being elevated to a design best practice...
This site is a disservice to the entire field of UI design, not to mention the users. At the very least they could have explained _why_ de-emphasizing secondary options or cropping information out of photos is "more correct"
To the site author: your suggestions considered harmful, just give me my 90s-era UI design back, please.
Then again, I'm not a UI designer. But I wonder what a UI designer thinks of someone boiling his/her design judgement down to a simple 'correct vs. incorrect' choice.
The page instead just makes it white, like it wasn't a button at all and we can only guess by the word only making sense for button
That would look absolutely whacky. Especially in responsive design, where the aspect ratio of the parent container changes with screen width.
The difference is that thumbnail images aren't TV shows, it doesn't really matter if the image is cut off. Its not supposed to have literal information, its just a contextual hint of what that element is doing / is related to.
Using color to differentiate actions is OK, if you are doing styling actions those are different than, say, templating actions.
Promoting obfuscation or misdirection as good design is inexcusable.
It's not so much about choosing the "better" design (although in most of these cases one of them is objectively better), but choosing the design used in the real app.
Ideally it should be regular button with outline and some greyish color, but not completely hidden button.
Btw. quite easy for someone working in QA.