61–70 of 115 posts
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.
Earlier quoted context omitted.
> This is just tacky. According to you. I think it's beautiful.
I personally don't like the current implementation. But I think they are doing some good work on this repo. Over the next year I expect it to mature quite a bit. Once I start using it on my current project, I will even contribute to the code base.
I find it strange there's so many different material design implementations (for the web, no idea how it's going on in android), shoudn't at least the CSS be centralized to avoid uneccesary efforts and then provide specialized packages for things like bootstrap, jQuery UI themes, angular, react etc that all use the same base CSS? I know it's probably utopic but it looks like there's a lot of "wasted" energy in these…
Earlier quoted context omitted.
IIRC, in the design guidelines longer animations should be limited to context switches, where anything under two seconds is "acceptable speed" and anything under half a second is "fast". There's no need to use the most extreme animations for minor actions in the interface, and the linked page is obviously a showcase, not a real application.
Showcase is no excuse. This was intented to extend bootstrap. The author clearly envisions people reusing these animations.
I find it strange there's so many different material design implementations (for the web, no idea how it's going on in android), shoudn't at least the CSS be centralized to avoid uneccesary efforts and then provide specialized packages for things like bootstrap, jQuery UI themes, angular, react etc that all use the same base CSS? I know it's probably utopic but it looks like there's a lot of "wasted" energy in these…
If Google released their own, then presumably these would mostly disappear. I guess Google's focus right now is on Android, although elements of Material design are appearing on things like Google Docs, so they'd think they'd release that publicly, just as Twitter did with Bootstrap.
How about don't slow down navigation to play an animation. Function over form. Every time. Never artificially slow your user down for the sake of "pretty". Pretty is subjective, snappy is objective and appreciated by everyone. The navigation feels like when I was 12 and wrote my first c++ program adding "cool loading animations" for no reason.
Earlier quoted context omitted.
What's some of the best UX design you've done? Can you tell me about affordances, and why the Materials design falls short on them? On desktop? On touch devices? 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…
We do need to let users know a touch has been registered. In some cases all you need is a color change. Other time, a slight fade in or small animation. But having content areas fly in for almost a whole second is overkill. That's why this site is a poor example of the technique.
having content areas fly in for almost a whole second is overkill
In the Material design, animations are also intended to increase affordance by showing what areas are interactive, without requiring the extra chrome of everything having 3D borders.
Nicely done. Shouldn't the wells – being "wells" – be inset instead of outset?
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.
> Design for design's sake. This is one of the most senseless things I've read in a long, long time. I guess you think "design" means "decoration".
Actually design is a very ambiguous word for me as a developer. I use it to include application architecture, and user workflows amongst other things, while many other people seem to think its all about the shinny pictures on the front page.