Live data from Hacker News

Material UI

material-ui.com

41–50 of 166 posts

Re: Material UI

#41
A few things looked slick but not particularly usable, but I found the flare animation on-click got old (and a bit slow) after a while. Might be worth toning that down a bit?

Re: Material UI

#42
I've never been a fan of material design and surely hope it doesn't become a standard. Design guidelines from a company that is widely known not to care about design? No thanks. Even Google Inbox shows how engineering-driven everything is at Google - the navigation is completely unorthodox (going back = drag down), like someone above decided "this is the way we do everything from now on" and nobody had the balls to question 'em. I'd never accept Microsoft's design guidelines or Google's. If you truly care about design, you'd stick to Apple's or develop your own, which frankly isn't too hard in CSS anyway, and it means you aren't tied to a particular OS feel or a big-corp policy.

Re: Material UI

#43
post #4

http://material-ui.com/#/components/buttons Aaaand the first three buttons are hidden until you hover over them. How visual designers keep making mistakes like this in the age of mobile browsing is beyond me. EDIT: As has been pointed out to me below, they have their use-cases. I still wouldn't put them as the first shown option though - they're not exactly the sensible default fall-back. Also, the menu doesn't work…

Also doesn't work for me in regular Firefox 33.0.3 (OSX).

Same issue here, but on Win8.

Re: Material UI

#44
I had a talk with myself at the weekend about making a concerted effort to cut out the snark when I comment on the web.... And I'm about to fall at the first hurdle.

Being "on trend" isn't good UI design. But I can see how we got here. Through OS X and iOS, Apple's UI ethos became the gold standard in UI design. It was so well designed that it was easy to imitate and by simply adopting the core elements of Apples UI language, stuff became intuitive and usable without the designer needing to understand "why" something looked the way it looked.

And then came a new trend, the current trend, that appears to me to be rooted in nothing more substantial than a desire to replace the old with something new at all costs. And when the likes of Apple and Google fall for the same trap, it's nigh on impossible for fundamental UI design knowledge to make itself heard above the noise of a million designers advocating the new and pointing to Apple for credibility.

You can see that I don't like Material. I also don't like iOs's new UI language. It doesn't work. Ive seen no evidence that it's any more useable and I struggle everyday to make sense of software and tools that have adopted these new trends so anecdotally, I have to say to myself that we're going the wrong way.

Re: Material UI

#45

The comments thus far are disappointing. People go to the trouble of making a pithy comment on hackernews, but surely since many of us here are developers we understand the frustration of bad bug reports. Is it so hard to bottle up your negative comments and spend another two minutes doing something constructive - like heading over to github and adding an issue with your system specs?

It's not "negative comments" to point out to other people what works and what doesn't.

Complain as much as you want about how I don't push fixes, but as long as I'm not paid those complaints are better kept to yourself.

(I realize you are not one of the developers for this project. I only want to illustrate how negativity goes both ways. I'm a bit tired of "contribute or shut up". There's a big gray area inbetween.)

Re: Material UI

#46
post #24

http://material-ui.com/#/components/dropdown-menu really? how can this be good usability. it's text and an arrow far, far away. this could be anything and does not in any way imply any kind of select action. if this is really implemented after the material design spec of google, than oh man, google really has an issue.

Here's the Google spec for this: http://www.google.co.uk/design/spec/components/menus.html#me... If you look at the menu with "All", "Family", "Friends", "Coworkers", initially it shows "All" and the arrow is immediately to the right of the text. I expect that if you select "Coworkers" then the arrow moves.

Yeah, I think standalone it should have the arrow right at the end.

When the dropdown is used in a form, it should have an underline, like so from the Material spec: http://material-design.storage.googleapis.com/publish/v_1/qu...

Re: Material UI

#47
Bug report: If I follow the "Demo" link from the homepage, the first demo ("Buttons") works but clicking on any of the others (via the left hand menu) e.g. "Dialog" doesn't do anything. No obvious errors in the console.

I'm using FF 33.0.3 on Win7.

Edit: looks promising though - just get them bugs ironed out! :)

Re: Material UI

#48
post #24

http://material-ui.com/#/components/dropdown-menu really? how can this be good usability. it's text and an arrow far, far away. this could be anything and does not in any way imply any kind of select action. if this is really implemented after the material design spec of google, than oh man, google really has an issue.

The dropdown also caught my attention it seems like it's a bit of a distance from the traditional dropdown in a sense that I think some users will have some trouble with actually realizing that it's a dropdown. Another complaint is the checkbox, there's no way to tell once something is checked off whether it's a picture or a form.

Agreed with this. In Android's Material spec (as well as the Android 5.0 implementation) you can always tell it's a checkbox.

However, in Google's Polymer project, the box totally transforms, as in material-ui. :/

Ex) http://material-design.storage.googleapis.com/publish/v_1/qu...

Re: Material UI

#49
post #47

Bug report: If I follow the "Demo" link from the homepage, the first demo ("Buttons") works but clicking on any of the others (via the left hand menu) e.g. "Dialog" doesn't do anything. No obvious errors in the console. I'm using FF 33.0.3 on Win7. Edit: looks promising though - just get them bugs ironed out! :)

Same here, iceweasel 33.0 on Debian Wheezy.
Post reply on HN