I don't understand why Google keep doing things specifically for Sketch, that is a proprietary, commercial application that doesn't even run in every OS available. Doesn't run on Chrome OS either. So why? Shouldn't be far better invest into some open standard like SVG, so Sketch users can use it as well?
In case you're a developer and following this video, there seems to be a typo at 12:13 where `npm install @material/text-field` should be `npm install @material/textfield` source: material.io/develop/web/components/input-controls/text-field/
They didn't even mention angular.....but react is always there, even in a Google conference. And the same with sketch, again what about windows users... But otherwise well done !
the Sketch plug-in is a partial collection of the old "stickersheets" that was available for Xd, illustrator etc... these files are now vanished on the new Material Website.. Dear Google, what are you doing?
I admire Material Design because of the philosophy behind its architecture. Anyways, please include a React codelab for Material Design components ASAP. Thank you, Google! 😉
Implementing MDC in my current app. Took a while to figure out how to get the libraries in, since the site's "Getting Started", doesn't really help at all. But using the codelab was a good resource for getting past that. I have to use Studio Canary though. A few views don't render in stable. Maybe because I'm importing from AndroidX as well and not the support library. All in all.. Loving the updated themes.
It's super confusing design guidelines and standards, I spend days to understand what is colorPrimary, Material Theme editor is considering colorPrimary as a background of BotomNav and colorOnPrimary as the icons and text colors. But in the BottonNav documentation, they say colorPrimary is the color with which your icon and text will be drawn on the BottomNav. There is no mapping between colors in beautiful Material Theme editor vs Colors in Android. New theme attributes doesn't work with the current version of material components, I am not sure if I am missing something or Google did not focus on Android but only focused on Web and iOS.
I prefer Material component from CosmicMind (github/CosmicMind/Material). This project is fully implemented with Swift while Google MDC iOS is still using objective-c. I didn't understand why don't they cooperate and create the powerful Material component for iOS.
Is an *Android* presentation. *Why* for gods sake, they started an example with iOS coding? Yes, Google support xcode as well, but its duty is *primarily* support Android.
Unfortunately it wasn't mentioned in this talk, but work continues on Angular Material. The new outlined buttons are now available material.angular.io/components/button/examples. Note that they are called Stoked Buttons there.
Unfortunately it wasn't mentioned in this talk, but work continues on Angular Material. The new outlined buttons are now available material.angular.io/components/button/examples. Note that they are called Stoked Buttons there.
Interesting to see that in MDC web they even mention Polymer. It is a pity. Polymer is a Google framework that generated a lot a buzz (like Flutter today), make a lot of promises and slowly sink. Nice basic idea, not so good implementation. Probably because any nice thing that someone do in web ground become a mess after some time. W3C is slow and doesn't have enough power to enforce strong standards, so web is full of incompatibilities and bloat.
Nobody will use material design in iOS app. And no big company will use material design in their Android app. Because the designers only create ui design for iOS, and then copy it over directly to Android developer.
I don't understand why Google keep doing things specifically for Sketch, that is a proprietary, commercial application that doesn't even run in every OS available. Doesn't run on Chrome OS either. So why?
Shouldn't be far better invest into some open standard like SVG, so Sketch users can use it as well?
In case you're a developer and following this video, there seems to be a typo at 12:13 where `npm install @material/text-field` should be `npm install @material/textfield`
source: material.io/develop/web/components/input-controls/text-field/
They didn't even mention angular.....but react is always there, even in a Google conference. And the same with sketch, again what about windows users... But otherwise well done !
Sketch is only for Mac, so yeah - kind of sucks that they couldn't publish this for something that is more cross platform.
the Sketch plug-in is a partial collection of the old "stickersheets" that was available for Xd, illustrator etc... these files are now vanished on the new Material Website..
Dear Google, what are you doing?
You can still find those here material.io/archive/guidelines/resources/sticker-sheets-icons.html
Why there is no android example but lot of iOS coding?
Oprea George they just want to show that they can do better even with the other platforms!
On android you don’t really have to change much.
outstanding move
I admire Material Design because of the philosophy behind its architecture. Anyways, please include a React codelab for Material Design components ASAP. Thank you, Google! 😉
Implementing MDC in my current app. Took a while to figure out how to get the libraries in, since the site's "Getting Started", doesn't really help at all. But using the codelab was a good resource for getting past that. I have to use Studio Canary though. A few views don't render in stable. Maybe because I'm importing from AndroidX as well and not the support library. All in all.. Loving the updated themes.
watched the whole vid, still dont know how to implement in WEB
google serves customers irrespective of their platform. That's why I love google
Android examples? Theme editor for windows??
It's super confusing design guidelines and standards, I spend days to understand what is colorPrimary, Material Theme editor is considering colorPrimary as a background of BotomNav and colorOnPrimary as the icons and text colors. But in the BottonNav documentation, they say colorPrimary is the color with which your icon and text will be drawn on the BottomNav. There is no mapping between colors in beautiful Material Theme editor vs Colors in Android. New theme attributes doesn't work with the current version of material components, I am not sure if I am missing something or Google did not focus on Android but only focused on Web and iOS.
I prefer Material component from CosmicMind (github/CosmicMind/Material). This project is fully implemented with Swift while Google MDC iOS is still using objective-c. I didn't understand why don't they cooperate and create the powerful Material component for iOS.
Is an *Android* presentation. *Why* for gods sake, they started an example with iOS coding?
Yes, Google support xcode as well, but its duty is *primarily* support Android.
th-cam.com/video/D7LB-QPxH9c/w-d-xo.html&t=4m31s
(sic) "Yes, Google support xcode as well, but its duty is primarily support Android"
It's not android presentation you moron, it's materiel design presentation, they can do it in css or whatever
why react? why not fully develop on vannilla js to be framework independent?
Mdc for react great but what about angular ? 😦😦
Unfortunately it wasn't mentioned in this talk, but work continues on Angular Material. The new outlined buttons are now available material.angular.io/components/button/examples. Note that they are called Stoked Buttons there.
What about Angular?
Unfortunately it wasn't mentioned in this talk, but work continues on Angular Material. The new outlined buttons are now available material.angular.io/components/button/examples. Note that they are called Stoked Buttons there.
4:58 Nope you only get one fun fact
How am I supposed to work on windows why always sketch
My experience with material design 2 is perfect on Pie
I'm definitely going to try
Interesting to see that in MDC web they even mention Polymer.
It is a pity. Polymer is a Google framework that generated a lot a buzz (like Flutter today), make a lot of promises and slowly sink.
Nice basic idea, not so good implementation. Probably because any nice thing that someone do in web ground become a mess after some time. W3C is slow and doesn't have enough power to enforce strong standards, so web is full of incompatibilities and bloat.
Material Design is cool, the girl is awesome :)
MDC in angular 6 🤔 that's sounds good
MDC iOS: infecting Apple platform with the right way to design applications... :-)
I use windows. I cant use sketch. Ur material website is too confusing, too many different sites, cant u just have one main site?. But well done!.
Web at 11:50
MDC React 👍
check out *Flinty Rolls* a *MATERIAL DESIGN GAME* now Available on PLAY Store
Add Vue officially
This is already outdated and terrible.
No one uses Apple products anymore. When is Google going to give Android some love?
Nobody will use material design in iOS app. And no big company will use material design in their Android app. Because the designers only create ui design for iOS, and then copy it over directly to Android developer.
whataApp has a design for ios and a different one for android
Material design is platform agnostic. UX designers will save a lot of time if their designs take the ideas from material guidelines.
That's not true
Eric Wang
Not true, it's a guideline after all
bad designers do.