For each of the major platforms, following the guidelines will at least make your app consistent with the other apps on the user's device, which is a decent-enough baseline. Going wild and re-inventing how a drop-down should look or how scrolling should work is probably just going to annoy the user.
Absolutely. I have long mentioned that Google got lucky that the initial search was a textbox on a white screen and nothing else.
If they had tried to do a portal or something like Yahoo! they would have failed miserably.
Till today, I haven't seen a good design from Google for anything complicated. Just look at what a mess Gmail is for instance.
Great engineers, horrible product and design folks.
All search engines look like Google search
All calendar apps look like Google calendar.
All maps app look like Google maps.
All email clients look like GMail
I'm not saying Google invented any or all of these but it sounds like you don't like it the colors or font but that's different from your larger point.
Show me an instance where Google's UI is radically different from industry norms and then you'll have a point.
Some of this shit is complex and complex things look complex.
Gmail is the first email client that arranges conversations like that
For what it's worth, I think Google's products are far superior to it's competitors, and I've never had issues with a site looking too Google, though I've been burned by some complex SPAs that were slow and buggy.
I’ll do you one better: try making a chart in Google Sheets.
What's your preferred way? Matplotlib? Seaborn? R?
For example, adding data labels to a scatterplot. Completely insane how they want you to do it.
Or removing the Y axis from a bar chart. Have to make the text size 11 and white. Why?
There's a lot of little things like this that are just mind-numbing.
I like native PowerPoint charts (not Excel) and R's ggplot2 personally.
These are subjective things. We can't make proclamations that say 'this is bad!'
Of course there are people who prefer any conceivable style you might bring up. That doesn't mean there can't be legitimate strengths and weaknesses between them, up to the point where "this is bad" is an accurate shorthand for "on most metrics of interest, this design is worse than its competitors."
People get up in arms about plenty of stuff that doesn't matter. Sometimes it's a matter of taste and the preferences are spread widely. Sometimes it's down to familiarity; "OMG CHANGE!" is a real thing. Sometimes it's a pet peeve that hardly anyone cares about. But that doesn't mean there can't be legitimate bases for comparison and opinions.
UX people complain, often rightly, that they receive excessive and unfounded abuse for decisions that are a matter of debatable preference. Abuse is bad. Opinions can be excessive or ill-conceived or reactive or abusive or whatever. But the pendulum has swung so far now that any complaints about UX are automatically dismissed as irrelevant and problematic. It doesn't matter whether you have a well-founded argument for your opinion; your opinion is unwanted and every word of your argument, every point you make, is seen as only proving that you're a jerk and a crank. "Trust the UX people." "It's not fair to complain about something when you're not the expert and they are." Yeah, whatever. I'm a user, and if I'm having trouble using, that should matter to someone who has some say.
</rant>
The problem comes (as you describe in a later post) if you don't just want a chart, but instead want a particular chart for a particular purpose. Not some weirdo crazy purpose, either; there are many ways to get into trouble trying to make minor adaptations.
Same thing with Material. It's great for making a bland clone of a thousand other interfaces, preferably one with only a handful of relevant interactables ("find the beige car" is hard when they're all beige). If you need to distinguish things that are different because they have a reason for being different -- say, labels and buttons -- well then you're SOL.
So, when Material Design came out, and it wasn't even distinguishing the extents of UI elements (e.g., transient UI object with same background as what it partially overlapped, with no border), it violated much of what we knew about HCI (i.e., in the interests of the user or task), and it looked like a brochure (i.e., in the advertiser's interests) more than anything else... Occam's Razor needed only to mutter the words "advertising company".
I know that some percentage of the people who have to work atop Material Design are doing good HCI despite it, but they're fighting against sabotage, and we all are dumber and less effective for it.
Because I assumed I knew what the argument was. I assumed this was another material ui doesn't look great -- while not appreciating the nuance of Google. Just as I assumed "what if I really want a faster horse" was actually about some anti-AI thing that just didn't appreciate how game-changing AI models are.
I pigeonholed the author based on my pattern matching of similar titles.
Then I clicked around https://rakhim.exotext.com/. Always curious about clean design. So clicked around on https://exotext.com/. Clicked on a few more blog posts of Rakim again and thought maybe they were ok. I was still a bit in pattern matching mode (stereotyping perhaps) assuming the author was like other people on Bluesky etc. Perhaps reactionary etc.
Then somehow in my clicking I saw a thumbnail of the author and I was like - oh that guy looks like me.
It's messed up it took me to this point to get there - but at least I persisted in trying to understand where they were coming from. At that point though I started to click around more and more and actually read the articles and I realized I agreed with all of them. Part of my appreciation was that Rakim had created exotext.com etc.
Just a cautionary tale to not pattern match prematurely. Premature optimization...
Though building in guardrails to prevent premature optimization is an important hack. E.g., faces really do matter in terms of slowing people down and taking them more seriously I think. And just building in anti-premature-optimization "tread" or friction for lack of a better word. E.g., avoiding click bait titles that people might pattern match on. It's not the author's fault but it might be more successful that way. Cause - really insightful blogposts. I feel like a fool for dismissing them at first. And yet I hope they get wider reach via perhaps subverting the ways we pattern match (not that I or other people should but I think based on other comments and how people pattern match on me - yet another tech bro, etc. - it exists...)
pphysch•3h ago