|
|
|
|
|
by bsimpson
2671 days ago
|
|
I love that people make and share things, and I hate to pour water on announcements. I admire the effort that went into this. That said, it makes me sad to see more fragmentation in the Material space. When Material launched, it was a set of design guidelines. A bunch of open source teams (like Material UI) stepped up and put together libraries that implemented those guidelines for specific view frameworks. This project looks like one of those efforts. Since then, the Material Components for the Web project has formed. It's staffed by Google engineers who collaborate with the designers who write the Material Guidelines. They faithfully implement the Guidelines and makes updates as necessary to keep pace with design changes. The project is designed to be wrapped by other libraries to work with specific view frameworks. I'd hope that any Material library for the web that's put together in 2019 would leverage that work. It will more faithfully follow the guidelines and be easier to maintain over time, because there's already a team of people responsible for maintaining the underlying framework. If you haven't already, take a look at Material Components for the Web. You might have a better time if you back Material Kit with it. https://github.com/material-components/material-components-w... |
|