31–40 of 115 posts
Earlier quoted context omitted.
What's the problem with animations? We have 8 cores with 3ghz+ and 16gb of ram to just render plain text?
What percentage of machines do you think have those specs?
I hope this doesn't take off. If bootstrap wasn't annoying enough, we'll soon have this abomination on every MVP site. Animation for animation's sake. Design for design's sake. This is just tacky.
This is one of the most senseless things I've read in a long, long time. I guess you think "design" means "decoration".
Shouldn't the wells – being "wells" – be inset instead of outset?
I know it's probably utopic but it looks like there's a lot of "wasted" energy in these kind of projetcs.
I hope this doesn't take off. If bootstrap wasn't annoying enough, we'll soon have this abomination on every MVP site. Animation for animation's sake. Design for design's sake. This is just tacky.
According to you. I think it's beautiful.
Earlier quoted context omitted.
What's the problem with animations? We have 8 cores with 3ghz+ and 16gb of ram to just render plain text?
Because it takes time and is distracting. An interface should be snappy and get out of your way, not try to impress with pointless animations. That screams graphic designer trying and failing to do UX. Which is material in a nutshell really.
For us developers, a command line and vim (or emacs, not trying to start a war) can be the epitome of UX -- once we learn all those shortcuts.
But for users, there's a lot more that comes into play. Indicating to a user when something can be interacted with and - more importantly, many times - how it can be interacted with is very important. Usually such indications will also inform about what kind of result will happen from the interaction: will the form submit, will the page reload, will I see a list of additional options?
Just as important is indicating to the user that yes - you just interacted with something that can be interacted with. Depending on the action, this can be something as subtle as an underline - or as obvious as showing a loading indicator.
The Material animations aren't just eyecandy for the sake of eyecandy. While touch screens are getting better, there are still situations where a touch doesn't necessarily register as a touch. It's super important to indicate to the user that a touch has been registered. It's just as important that this happens immediately, instead of after - say - a round-trip request to a server somewhere.
If you've built and designed a user interface that has amazing affordances, a general perception of 'speediness' even if the server is being slow, and treats touch users as a first-class citizen ... I'd really like to see your work!
This is basically unusable on an iPhone 5S - text/elements bleeding off the panel, unclear scroll areas (easy to swipe the background scroll area). I thought the big use case of MD was to deliver a more intuitive interface especially on mobile. This misses the mark by a wide margin.