So, I just wanna say I am absolutely, incredibly excited for this. I've loved the design of paper-elements, but I don't want to attempt integrating Polymer into my projects.
That being said, the use of BEM is a huge turn off. The markup for a simple card uses seventeen different classes, which is absolutely a nightmare to memorize. For comparison, a card from Materialize uses only five to seven classes (depending on the type of card).
However, since this is built in SASS, I assume you could use the extend keyword to combine a lot of the frequently used together classes into something more manageable. I haven't really used SASS in this way, so I'm not sure how that'd work.
Thanks for the feedback. We used BEM as we find it helps with the long-term maintainability of CSS/SASS codebases (there's also copy/paste support on all of our snippets). That said, if you find the use of BEM a turn-off, we welcome folks just taking our styles and adapting them to the naming scheme that makes most sense for them. Anything that helps.
I'm curious, what's keeping you from trying Polymer? Its paper-elements are a very good implementation of Material Design, and the library is very light weight.
Great news that Google has started this library. This will help MD implementors like me.
"That said, the large, diverse number of implementations available are often quite liberal with their interpretation of the spec (not their fault!) and their opinions don’t always reflect what the Material Design team would consider ‘correct’."
Nevertheless I found a number of deviations from the design specs:
- Disabled buttons should not have a z level
- FAB ripples should originate from the center
- Icon buttons should have a touch area of at least 40px
- The same goes for slider knobs (at least 30px, already small)
On the website:
- The scrollable tabs on the site are scrolled just a couple of pixels per arrow click, instead of scrolled per tab
- Scroll areas should have -webkit-overflow-scrolling: touch, the current site is not scrollable on Mobile Safari
Great implementation of Material Design, the best I've seen so far. With other material design implementations [1] I ran into problems with checkboxes, sliders and other design choices, as well as problems on mobile. I appreciate the design choices made for MDL. It also runs smooth on mobile and the form elements like checkboxes and sliders work really nice.
Also, useful documentation along with codepen and easy clipboard buttons.
The ripples drive me crazy. Everytime I click a button my mind gets yanked into "what just went wrong?" because of the inconsistent nature of the ripples. Even though I know it's going to happen.
I dislike the abundance of color schemes with low saturation. This lower contrast, and I can imagine I'd have to turn up screen backlight to the max if I used it in sunlight.
I tried to use colleague's android and I found it unintuitive to use too (it wasn't obvious what elements you can interact with, and animations were annoying).
It's like saying in a Windows 10 thread you dislike the MetroUI/ModernUI design.
I prefer the material design in Android 5+. And I like the iOS 7+ design and Win7 Aero design. But I cannot live with the ModernUI of Win8/XboxOne - who choose those ugly colors?
I think we need to be careful of treating Material as an all encompassing solution. A lot of UI / UX folks I know are full on embracing it without taking a step back and seriously evaluating what problems it will and won't solve. I'm not saying I dislike it, I just think that there are different solutions for different situations. There is no silver bullet in our industry.
I was thinking the same. I initially thought based on the name I could pick a single component to use but its an entire framework, so it still suffers from bloat.
Are you saying that's a good thing mainly for performance reasons?
I ask mainly because I vaguely remember someone running the numbers and finding out that js animations surprisingly beat CSS animations in a number of not-unrealistic scenarios.
(I know there's other reasons for favouring CSS animations)
If there are any animations at all you find are janky, could you file and we'll look at it soon? We've been performance testing on a wide range of devices/browsers but I'm certain there are plenty of areas we can improve on.
Lead for MDL here. Glad you like the idea, spoiler :) Thanks for catching the low contrast issue with the dashboard navigation - is it the same as https://github.com/google/material-design-lite/issues/739?. If not, would you mind filing an issue on the repo and we'll try to get that fixed up soon?
The Material Design Lite website (http://www.getmdl.io) breaks scroll behavior on mobile Safari.
If you're promoting a UI/UX product, you really shouldn't be bungling scrolling. Because if you can't get your own site working well, I'm not trusting your libraries on my site.
Ohh the BEM bummer. All those __ and -- makes my eye hurt. Write decent line of code in HTML file with BEM classes and it looks worse than inline styles (visually).
For the rest of library, I'm still trying and testing, but I don't think I'll be moving any of my main projects to this library because of BEM.
Thank you for this. I still feel like the Material Design implementation within Polymer is rough around the edges. Having issues with Firefox, for example, in terms of optimization and documentation is still very incomplete. Looking forward to working with both libraries, though!
Outstanding library. I like this version of material more than the other with polimer that's completeley flat.
There are some issues with scrolling in general and with scrolling with tooltips open on ios, but will follow and see if they eventually get around those.
Agreed. This project is awesome but without usable form elements (there's more to forms that text fields) this isn't really usable for anything a little more complex.
[+] [-] dstaley|10 years ago|reply
That being said, the use of BEM is a huge turn off. The markup for a simple card uses seventeen different classes, which is absolutely a nightmare to memorize. For comparison, a card from Materialize uses only five to seven classes (depending on the type of card).
However, since this is built in SASS, I assume you could use the extend keyword to combine a lot of the frequently used together classes into something more manageable. I haven't really used SASS in this way, so I'm not sure how that'd work.
[+] [-] addy_osmani|10 years ago|reply
[+] [-] spankalee|10 years ago|reply
[+] [-] ArthurClemens|10 years ago|reply
"That said, the large, diverse number of implementations available are often quite liberal with their interpretation of the spec (not their fault!) and their opinions don’t always reflect what the Material Design team would consider ‘correct’."
Nevertheless I found a number of deviations from the design specs:
On the website: Author of Polythene for Mithril, https://github.com/ArthurClemens/Polythene[+] [-] addy_osmani|10 years ago|reply
[+] [-] matthijs_|10 years ago|reply
Also, useful documentation along with codepen and easy clipboard buttons.
Following.
[1] To name a few material design examples: http://superdevresources.com/material-design-web-ui-framewor...
[+] [-] TranquilMarmot|10 years ago|reply
[+] [-] qwreasdfkjhiouy|10 years ago|reply
[+] [-] mattmanser|10 years ago|reply
[+] [-] bluthru|10 years ago|reply
[+] [-] zvrba|10 years ago|reply
I tried to use colleague's android and I found it unintuitive to use too (it wasn't obvious what elements you can interact with, and animations were annoying).
(I'm a WP user and it's THE UI I like best.)
[+] [-] frik|10 years ago|reply
I prefer the material design in Android 5+. And I like the iOS 7+ design and Win7 Aero design. But I cannot live with the ModernUI of Win8/XboxOne - who choose those ugly colors?
[+] [-] Saturnaut|10 years ago|reply
[+] [-] trenta|10 years ago|reply
[deleted]
[+] [-] philtar|10 years ago|reply
[+] [-] philliphaydon|10 years ago|reply
[+] [-] okpatil|10 years ago|reply
[+] [-] paulirish|10 years ago|reply
[+] [-] thirdsun|10 years ago|reply
"-webkit-overflow-scroll: touch" seems to be missing on the main content if I had to guess.
[+] [-] marcacohen|10 years ago|reply
[+] [-] Aldo_MX|10 years ago|reply
[+] [-] andybak|10 years ago|reply
I ask mainly because I vaguely remember someone running the numbers and finding out that js animations surprisingly beat CSS animations in a number of not-unrealistic scenarios.
(I know there's other reasons for favouring CSS animations)
[+] [-] TheSisb2|10 years ago|reply
[+] [-] addy_osmani|10 years ago|reply
[+] [-] weitzj|10 years ago|reply
[+] [-] vijayr|10 years ago|reply
[+] [-] fiveseven_|10 years ago|reply
more info here: https://medium.com/google-developers/introducing-material-de...
[+] [-] 4x3l|10 years ago|reply
[+] [-] JohnTHaller|10 years ago|reply
[+] [-] spoiler|10 years ago|reply
I have to point out some flaws, though; for example the side menu here[1] has very low text contrast once you hove over them.
[1]: http://www.getmdl.io/templates/dashboard/index.html
[+] [-] addy_osmani|10 years ago|reply
https://github.com/google/material-design-lite/blob/master/C...
Alternatively, we can file a bug for you if you share details about the browser/os/device you were testing on.
[+] [-] Zikes|10 years ago|reply
[+] [-] freyr|10 years ago|reply
If you're promoting a UI/UX product, you really shouldn't be bungling scrolling. Because if you can't get your own site working well, I'm not trusting your libraries on my site.
[+] [-] asurma|10 years ago|reply
[+] [-] sancha_|10 years ago|reply
[+] [-] bikas|10 years ago|reply
[+] [-] ConAntonakos|10 years ago|reply
[+] [-] shenzhuxi|10 years ago|reply
[+] [-] LoSboccacc|10 years ago|reply
There are some issues with scrolling in general and with scrolling with tooltips open on ios, but will follow and see if they eventually get around those.
[+] [-] gbrits|10 years ago|reply
[+] [-] _ari|10 years ago|reply
[+] [-] pan69|10 years ago|reply
[+] [-] rtpg|10 years ago|reply
Depth is such an important part of the nice look of Material Design that not having it seems like a big mistake
[+] [-] ranyefet|10 years ago|reply
[+] [-] asurma|10 years ago|reply
[+] [-] applecore|10 years ago|reply
[+] [-] JohnTHaller|10 years ago|reply