What's next for Material Web Components in 2024 #5402
Replies: 12 comments 32 replies
-
I just started using MWC with Vue 3 (and Vite) and so far it's a breeze. "It just works". I hope that improving the experience with React doesn't detract from this. The biggest issue I've run into is that the material-color-utilities are not up-to-date in what they produce. Also, the API docs are missing the slot information (I saw a ticket open on that). Something that would be great is to start a "using MWC with Vue" page and let the community provide additions (or perhaps this should start as a discussion thread). |
Beta Was this translation helpful? Give feedback.
-
|
Great! Thank you for your efforts. |
Beta Was this translation helpful? Give feedback.
-
|
I would really a focus on using web components as replacement for traditional form elements rendered in server side frameworks like django. Also importing individual components as esm would be nice to have. |
Beta Was this translation helpful? Give feedback.
-
Hey guys! really love the components so far! I made a python script that will generate a file that other devs can paste into the root folder of their React project, and it would make all the components in @material/web available to use in React. This is all based on a workaround that one of the actual devs for @material/web suggested found here. I tried my best to write a read.me for it that would help users on how to use the script, and how to actually use the @material/web components in React. Here's the repo! https://github.com/brandonsbque/custom-component-gen . Hopefully, I'm not breaking any Github or you guys' policy here by linking my repo, since this is the first time i've done something like this, but if so please let me know! I hope this helps others 😄 I would really appreciate it if you guys gave some stars on the repo too if you found it helpful 🤩 |
Beta Was this translation helpful? Give feedback.
-
|
Does this mean we won't see the rest of the components until 2025? |
Beta Was this translation helpful? Give feedback.
-
I think so too. I would love to contribute to this project. |
Beta Was this translation helpful? Give feedback.
-
|
@christophe-g thank you, I'm frustrated as well 😞 I know just commenting can feel helpless, but we need more people to make comments like yours that show why we need to support this library and how not doing so impacts Google's brand identity. |
Beta Was this translation helpful? Give feedback.
-
|
Also, for anyone who wants to help out, start by joining the lit.dev/discord #material channel. We can talk more there :) |
Beta Was this translation helpful? Give feedback.
-
|
Hi @asyncLiz Thanks for your effort. I really like this project and I believe google are connecting design and development. I would like to contribute but I cannot join your discord by the link you provide 🥲 |
Beta Was this translation helpful? Give feedback.
-
|
@Danielnewheart try https://lit.dev/discord |
Beta Was this translation helpful? Give feedback.
-
|
too slow |
Beta Was this translation helpful? Give feedback.
This comment was marked as disruptive content.
This comment was marked as disruptive content.
-
|
What do you mean @mindaugasvcs ? It's literally identical, what a silly comment. |
Beta Was this translation helpful? Give feedback.
-
|
Please remember to be respectful and follow our code of conduct. Thanks :) |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Use version 0.X, 1.X is beta and will have some bugs. You see one little issue and it looks and feels awful huh? @mindaugasvcs please stick to this repo and do not use the one I mentioned, you are not welcome there. |
Beta Was this translation helpful? Give feedback.
-
|
With all due respect, is it possible that you have not completed the development of MD3 yet and MD4 has already been released. |
Beta Was this translation helpful? Give feedback.
-
|
There is no such thing as MD4 afaik. |
Beta Was this translation helpful? Give feedback.
-
|
I don't agree with the roadmap; why focus on accessibility, expanded tokens, ... when essential components like navigation drawer are not yet implemented? Without these, nobody can use the library... Also, no need to focus on experience improvement with react, they have great libraries on their own. I recommend focusing on vanilla JS usage |
Beta Was this translation helpful? Give feedback.
-
|
Totally agree. I'm already moving away from this library based on this roadmap, none of those things help me. And 100% on the react comment, they don't need yet another library. |
Beta Was this translation helpful? Give feedback.
-
|
Totally agree. This is roadmap's problem. very silly problem. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for all the great efforts! Any plans or supporting Material 3 Web Components for Angular too? E.g. Md-checkbox vs the older Mat-Checkbox, with all the new Material 3 customisations? |
Beta Was this translation helpful? Give feedback.
-
|
https://material.angular.io/guide/material-3 |
Beta Was this translation helpful? Give feedback.
-
|
@asyncLiz |
Beta Was this translation helpful? Give feedback.
-
|
Meanwhile in 2025 I'm still stuck on Material 2 as Navigation Drawer and Cards still appear to be "planned"! |
Beta Was this translation helpful? Give feedback.
-
|
Card and nav drawer are in this fork: https://github.com/treeder/material |
Beta Was this translation helpful? Give feedback.
-
Why don't you contribute them to MWC? It would be really good to avoid having to install MWC from several sources... |
Beta Was this translation helpful? Give feedback.
-
|
Because this project is dead. And you don't need to install from several sources, just pick one. |
Beta Was this translation helpful? Give feedback.
-
This is the main reason to everything. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
tl;dr our roadmap is updated for 2024!
This year we are working on accessibility, TSX support, expanded tokens, and three new components.
Happy new year everyone! 🥳
2023 was a big year for us: we launched @material/web 1.0 with 19 production-ready components. It was quite the sprint involving a full rewrite AND design system overhaul for Material 3! 😱
This year post-release, we're focusing on sustainable, helpful, and realistic goals. Here's what's coming next!
Check out our updated roadmap for all the details! (there's some juicy bits on prototyping Material layouts 👀)
Thank you all for your continued feedback and support!
❤️ The Material Web team
Beta Was this translation helpful? Give feedback.
All reactions