Live data from Hacker News

Material UI

material-ui.com

21–30 of 166 posts

Re: Material UI

#21
post #13

Earlier quoted context omitted.

> couldn't find the tiles however So you mean, not Metro at all right?

There used to be in the original copy, here is a saved image at the top: http://www.eyeonwindows.com/2014/06/25/googles-material-desi... Maybe they couldn't reconcile them with other alterations or are simply trying to respond to criticism.

That image has nothing to do with material design and cards have nothing to do with tiles. It's very far-fetched to even suggest that Material design and Metro UI are even remotely similar.

Re: Material UI

#22

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…

Google's design guidelines advise using flat buttons "for contexts such as toolbars and dialogs to avoid gratuitous layering". Seems to me there may be cases where they are useful.

http://www.google.co.uk/design/spec/components/buttons.html#...

Re: Material UI

#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.

Re: Material UI

#26

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?

Heading over to github would help the project, it is true.

But HN isn't only a place where people come for help. It's also a place where people come to share. And when low-quality (or not-yet-production-ready) work is shared, it's important that we let each other know that. Especially when the site seems to imply it's "ready", as this one does.

Re: Material UI

#28

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?

I visited the site on my Windows Phone 8.1, and the page is rendered incorrectly. There's white text on white background, different text sections overlapping eachother, columns being one word wide and lot of more things. According to other comments here, it is unusable on iphone and broken on android as well. According to issues in their tracker, it does not work on Windows 8/Firefox and Ubuntu/Firefox.

It also renders incorrectly on Chrone om Windows 8 (on my laptop, at least).

If you're creating a new CSS framework, publish it and fail to mention that it's work in progress and it only works on a limited set of platforms (like what), you have wasted my time.

I really hope developers doesn't expect to only get constructive feedback when doing something like that.

Re: Material UI

#29

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…

Google's design guidelines advise using flat buttons "for contexts such as toolbars and dialogs to avoid gratuitous layering". Seems to me there may be cases where they are useful. http://www.google.co.uk/design/spec/components/buttons.html#...

Fair enough. I still think putting them first is sending the wrong signal though: using a flat UI should be a deliberate, carefully evaluated choice (like the example you gave). Not the default.

Re: Material UI

#30
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.

> it's text and an arrow far, far away.

That's an arrow? I just see a Unicode failure-box :(

That's one of the problems with the trend of icons-as-fonts, when they fail there's no reversion mode for users to understand what the glyph is supposed to be.

planefinder.net is a canonical example, without the correct font none of their on-screen controls make any sense.

Post reply on HN