111–120 of 154 posts
I basically associate material design with "slow" now, especially ever since Google has began to move all their services (flights, analytics) to material design. It's all becoming slow and annoying to use, anyone else feel the same?
I dunno, looks slick but I do wonder how much of this is actually useful for building an admin interface. Once I've got decent form styles and a navbar I find that most of the rest is either very simple, or very application specific. Widgets are cool, but mostly we need tables and forms.
> Widgets are cool, but mostly we need tables and forms. This (though I agree with sibling comment about a few more being useful). I reviewed 20 popular admin themes last month for our startup, and was v disappointed with them. Either due to code quality, or throwing in loads of useless widgets which are more consumer rather than business oriented. There's a gap for a theme that's more like Stripe's dashboard, not th…
Do people actually like Material for browsers on desktops? I tried it - as it would be great to have an opinionated design language with good framework implementations but it seems to make the same mistake as Windows 8 in trying to treat everything like a phone. That really isn't nice on a desktop.
I like Home Assistant and don't hate the Google Cloud Console.
Earlier quoted context omitted.
> I also find the ripple effect[1] when pressing things to be infuriating. Just do the action I've asked, don't do this animation and delay the action by half a second. Again, this is somewhat irrational, but it still bothers me. It is not irrational to want your device and the software you use on it to be as high-performance as possible. In my opinion, unless we're talking about a game, software should always avoid…
Yes, and no. While nobody likes excessive animation, it is very important to let the user know their input was received. It's why the cursor changes on mouseover. It's how you know if the app is crashed, or merely processing something you requested. I've seen a million times in UX testing where ordinary people go click... wait... click click click click click because they didn't receive any feedback to an action. At…
On mobile, this is more difficult - the user's finger is obscuring whatever button they hit from view, so I kind of understand the "ripple" after the button is released (and ostensibly the user's finger has moved away, thus allowing them to actually see the ripple).
Still, unnecessary delay is infuriating on desktop apps. I agree feedback is important, but I don't accept the premise that latency is required to provide feedback.
Do people actually like Material for browsers on desktops? I tried it - as it would be great to have an opinionated design language with good framework implementations but it seems to make the same mistake as Windows 8 in trying to treat everything like a phone. That really isn't nice on a desktop.
It's rather amazing how little information can fit on a screen with these designs even with modern high-res 4k retina displays. It's a failure of following trendy UI instead of focusing on true UX.
Earlier quoted context omitted.
One of the banks I used "updated" their iOS app and used Material Design. It's infuriating. The thing that bothers me the most is the "switches" (3rd example here[0]). My first thought upon updating the app was "Why did they reinvent the toggle switch when iOS has a perfectly good one built in?" Being bothered by this is irrational, yet I'm bothered by it all the same. I also find the ripple effect[1] when pressing t…
> I also find the ripple effect[1] when pressing things to be infuriating. Just do the action I've asked, don't do this animation and delay the action by half a second. Again, this is somewhat irrational, but it still bothers me. It is not irrational to want your device and the software you use on it to be as high-performance as possible. In my opinion, unless we're talking about a game, software should always avoid…
My iPhone 8 still takes me just as frustratingly long to navigate apps as it did on my iPhone 4, because there's no way to skip the useless animations and effects.
Earlier quoted context omitted.
Yes, and no. While nobody likes excessive animation, it is very important to let the user know their input was received. It's why the cursor changes on mouseover. It's how you know if the app is crashed, or merely processing something you requested. I've seen a million times in UX testing where ordinary people go click... wait... click click click click click because they didn't receive any feedback to an action. At…
> While nobody likes excessive animation, it is very important to let the user know their input was received. It's why the cursor changes on mouseover. It's how you know if the app is crashed, or merely processing something you requested. I said, "Of course, if an animation is playing while something else is happening, that is acceptable." Yes, play an animation while actual work is happening. That provides the feedb…
*https://developers.google.com/web/fundamentals/performance/r...
Are they easy to work with? Adjust to your own circumstances?
I ask because, while easy on the eyes, they strike me as somewhat complicated and you wonder if you'd be better off starting from scratch or something simpler.
Earlier quoted context omitted.
>well thought out design language I see it as less "well thought out" and more "designed into meaningless oblivion." I don't know anything about how Material was put together, but from an outsider's view it looks like something that came out of a committee of committees of committees.
I think in technology circles people just love to complain. They think it makes themselves look smart for some reason. Personally I'm a fan of MD and other minimalist styles. But it doesn't matter what technies think. What matters are the users. Google did extensive usability testing on MD but just to be sure we did our own testing because we weren't sure how it would go over in Asia and Google is less focused on the…
Earlier quoted context omitted.
> While nobody likes excessive animation, it is very important to let the user know their input was received. It's why the cursor changes on mouseover. It's how you know if the app is crashed, or merely processing something you requested. I said, "Of course, if an animation is playing while something else is happening, that is acceptable." Yes, play an animation while actual work is happening. That provides the feedb…
The RAIL* model for user-perceived performance does a really nice job of distilling rules of thumb for latency into a handful of specific metrics / perf targets. * https://developers.google.com/web/fundamentals/performance/r...