Closed rugk closed 5 years ago
Do we want material design?
I really would like to use it because then the website and the app are using the same design principles and users don't feel unfamiliar with the interface...
Do we need a lib for that? Do we even may use so much elements of it?
As libraries really can support you to write and maintain less code and it also helps to add new features easily, I would say, Yes, we should use a library (just makes things a lot more easier...) I already worked a lot with Materialize (thought it might be simpler to use) and I never used Material Components (I looked at the docs some time ago and it looked a little bit over complicated 😄...)
Choose a small lib that suits our task? (not too much) I guess, we hardly need many icons, fonts or so, or do we?
The material icons are not mandatory to use e.g. Materialize and I would prefer to not use them as this is just an unnecessary huge file and we will never need 950 icons for our project 😃
Okay, can we compare materialize and material components. Is there a big size difference?
Also found "Material Design Lite": https://getmdl.io
This aims to be small and has no JS, which sounds good IMHO, at first.
But is owned by Google: https://github.com/google/material-design-lite
Well… if it works and is properly designed, i see no problem with that. (Obviously, we don't need to use any CDN-hosted version, but that applies to all libs.)
So we'll choose materializecss.com for now.
And "Material Design Lite" is outdated as it points to "material-components-web" now…
Questions
Choose