71–80 of 166 posts
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! :)
After having seen the buttons, I've seen enough. I'm not bought so far.
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…
I don't find this post snarky, but from a usability point of view I'd love to hear specifics about where you think these designs fail?
I actually like the 'flat' look, but one thing I hate is the drop-down menu in Chrome for Android. Here's what I'm talking about: http://goo.gl/41iRZk
When the menu is displayed it takes about half a second to display. Every menu item is...slowly...faded...in...one...after..the...other. Give me Windows 3.1 where you click and the menu displays instantly!!
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…
I was recently looking into libraries to use Material Design with React.js. I found the material-ui project to be implemented less well than this one: http://sanderspies.github.io/react-material/ (though I have my reservations about the approach taken here, too -- and it's less complete).
"This project is still in early preview."[1] Worth keeping an eye on if you are working on any angular projects.
Not to take away anything from OP's, I feel their implementation of material is a little closer to the mark.
[0]https://material.angularjs.org [1]https://github.com/angular/material
Earlier quoted context omitted.
The primary principle at least from the point of Apple is to turn the actual content into the UI by allowing for a different kind of visual depth. What you see right now is first steps towards a UI that will use animation to create a sense of depth and perspective rather than using static visual design to imitate the world around us. So think about Googles Material Design and Apples iOS design paradigm as a return to…
Relying on animation to provide depth and perspective may not be a great idea. Subtle static cues remain a constant reminder on the display even if you aren't focused entirely on the application. Animation is much more heavy handed and isn't always there. If the user misses the transition animation, how do they know how to interact with the resulting static page? Animation also has the potential to slow down users as…
Such as... shadows? which help in feeling depth statically, which is what Material Design is about. What I feel is that MD is young and has rough edges but rests on solid principles.
> Animation also has the potential to slow down users as they become accustomed enough to the interface to know which elements they want to interact with before the animation completes.
Interestingly consistent animation time can have a bonus effect, as a "slow" loading element and a "fast" loading element are paced, creating a temporal rhythm in interface action for those accustomed to the UI, instead of a randomised, off-beat staccato. You don't just know "where" this button will land, you also know "when" and you can get there without visually polling and parsing the screen for availability.
This is all a game of balancing opposites. I totally loathe brutal reflows and interface pop-in (to the point I disabled Chrome's new tab page[0]) because it just triggers an interrupt->parse->interact cycle whether or not I know where to go.
[0]: https://chrome.google.com/webstore/detail/empty-new-tab-page...
I have been using the angular team's material design project[0] with great success. "This project is still in early preview."[1] Worth keeping an eye on if you are working on any angular projects. Not to take away anything from OP's, I feel their implementation of material is a little closer to the mark. [0] https://material.angularjs.org [1] https://github.com/angular/material
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 should always be possible to submit bug reports and comments anonymously, or as a "guest".
Making it difficult for users to report bugs is stupid, and harmful. While some people do already use GitHub, there are more of us who don't.
It's bad enough that I had to create an account here to post this comment. I refuse to go through the more extensive GitHub signup just to report a bug affecting software I don't really care about.
Earlier quoted context omitted.
I don't find this post snarky, but from a usability point of view I'd love to hear specifics about where you think these designs fail?
> I'd love to hear specifics about where you think these designs fail? I actually like the 'flat' look, but one thing I hate is the drop-down menu in Chrome for Android. Here's what I'm talking about: http://goo.gl/41iRZk When the menu is displayed it takes about half a second to display. Every menu item is...slowly...faded...in...one...after..the...other. Give me Windows 3.1 where you click and the menu displays ins…
While I like the project and effort put into this, I think, if you considering using this project, you should also look at google's own polymer project. Its based on the industry standard web-components. https://www.polymer-project.org/ React is using "virtual dom" which is kind of a hack to support web-components kind-of technology. Since the technology is currently here, i would recommend using it, and not using Re…
Is this correct? React doesn't use the virtual DOM to create HTML-like elements, it uses JSX for that, and JSX is optional. As far as I know the virtual DOM is used to avoid updating the "real" DOM in the browser when you don't have to.