Material Design for Bootstrap
fezvrasta.github.io
fezvrasta.github.io
I personally think it matches the Google's implementation a little better, but that isn't to take away from the great work you've done.
One thing I noticed off the bat, is that the buttons have a shadow on them by default, not just on hover. And the click animations are slightly better.
But again, great work to you.
I'm not sure I can quite get used to this particular theme at all. The colors are pretty gaudy, the main action buttons (brown and purple) particularly are almost unreadable to me. I couldn't find the input boxes at all even though they had a header, they just parse as horizontal rules rather than something I can click on an add text. I respect the effort that has gone into creating this, but on a fundamental level I don't feel this is a good step in interface design.
I just find "material design" obnoxious, pathological cargo-culting and can't bring myself to elocute it, except maybe if I'm referring to someone designing synthetic leather.
The flat/shadowy UI elements are secondary IMO to the layering effects that have been added. Something bootstrap themes can't really capture.
... and bright colors, yeah.
But it's really just a return to early 90s GUI design (flat, high-contrast, shadows): http://files.vforum.vn/2013/T08/img/diendanbaclieu-98580-tur...
This is a good start and could be really great, but it but needs some refining before it can be considered a true implementation of Material Design.
Firstly, it's too constraining, too specific, this style could get pretty boring and bland if every app uses it. And for lots of apps (and majority of webs), different spacing, structure, etc. is optimal – forcing them to use a different spacing would lead to worsened usability and ugliness.
Secondly, the animations can get annoying and distracting quickly.
Yes, most of the animations feel unnecessary.
I can't find any complex UI examples. Really want to see what it looks like when there are more than a few elements.
For now I wouldn't use it in production (broken build, not complete, etc.) - but it might be a start for what you want.
https://www.dropbox.com/s/hk24p7rjillampz/Screenshot%202014-...
I'm not sure I like the material design too much (not a slight against your designing) but I think it's more suited to application-style websites and whatnot.
That said, I appreciate the link and only time will tell... it's what I said about flat design as well, and I love flat now :)
For comparison, all the polymer demos for material design run buttery smooth.
- The inputs don't look like inputs.
- The animations on the navbars are really strange.
- The breadcrumbs are really out of place.
- So are the labels and panels. The colors are entirely wrong.
- Selects look weird.
- The contrast on the buttons at the top is atrocious. If I turn down my brightness I can't read the button text.
Other than that, it looks good.
If it can be boiled down to just another bootstrap theme, then it's pointless.
On windows phone 8, it has an odd button highlighting deal, and on iOS 8 there is an uncomfortable 800 or so millisecond delay.
The fact that someone outside of Google had to build this makes it look like Google's design guys have no credibility inside of Google, and are ignored by other Google devs.
The ionic team is helping build angular specific material components. Google should have cleaned up its own stuff here.
Its early days, they're clearly doing this first with Android L, Web Components (polymer-project.org) and Angular (material.angularjs.org).
And you're upset the implementation for Bootstrap is not done by Google? Boo hoo.
Android L is also shipping with Material Design widgets: https://developer.android.com/preview/material/index.html
Google doesn't really use or promote Bootstrap (much... we're* so big I'm sure it's used somewhere), and Bootstrap is designed for a pre-web components, pre-flexbox world, so it shouldn't be too surprising that we didn't release a theme for it.
* I work for Google
---
aside: I now strongly believe that, by HTML10, no elements will be defined and everything is going to be JS, and then there is going to be a massive HTML5/6 movement, "Hey guys, did you know that its possible to get /native forms/ though the web browser? and it doesn't even require javascript, manages to support in-built validation, you can even have 3d animations, all built-in to the html5 framework!"
Javascript is also currently faster for animating, and can do a wider variety of animation.
so many blogs I've seen that require JS, when all they serve is text content...
I'm not saying Google has any obligations to offer more code to support materials design... I'm just saying the impact of their design work is going to be limited because of it. (That certainly might be on purpose,I suppose)
I didn't like the save icon.