Thanks to all the team!

I agree thank you to the team! I am looking forward to a return to this from the Google dev team... please don't let them Game of Thrones Season 1 this product 🙏🏾

Unfortunately no. The older MDC project is deprecated. It will not be updated or maintained.

The MDC's project readme should be updated soon to reflect this.

Unlike MDC, Material Web Components isnot deprecated. While Material isn't staffing it's development, we're still trying to find ways for it to be community driven or find new maintainers.

I seems MDC is still getting updates when I look in the Git history, also Angular Material seem to be using a version 15.0.0-canary.7f224ddd4.0 of MDC when I look in the packages.json. What is the relation between the Angular Material project and MDC. Are the Angular Material project still updating MDC and could they release a version 15 at some point?

Any commits you might see on the MDC repository are a side effect of work to remove MDC as a dependency for both Angular and Wiz. There will not be an MDC v15 release.

I have acouple ofcomments in this discussion that offer more insights on Angular, but the best place to ask would be on theAngular components GitHub repo.

@jensborch here is an official statement from Angular Team on that matterhttps://blog.angular.dev/the-future-of-material-support-in-angular-7fa0662ecc4b

This library is awesome. Way more feature complete and easy to use. I already created a PR for Aurelia 2 integration I'm working on:zdhxiong/mdui#322

Looks great, but keyboard navigation does not work on the documentation page. Was it disabled somehow, or accessibility is not supported yet?

Looks great, but keyboard navigation does not work on the documentation page. Was it disabled somehow, or accessibility is not supported yet?

Keyboard navigation is supported; if it doesn't work, there may be bugs. Accessibility is not fully supported yet.

I looked at it and really like it. I want to use in my designer (https://node-projects.github.io/web-component-designer-demo/index.html) but the manifest seems to be wrong. Created and issue.

This library is awesome. Way more feature complete and easy to use.

@mreiche Same good feeling to use it withhttps://web-cell.dev/ :
zdhxiong/mdui#325

See above (mdui).

Thank you for being such an amazing tester and contributor! 😭

people do not need to migrate. the existing components are pretty stable and reliable. moving people around an org happens all the time, this project is far from abandoned/dead.

@43081j I have been following MWC & Material Web for 3 years at least:

• https://github.com/EasyWebApp/material-cell
• https://github.com/EasyWebApp/material-cell-document

The official Web components libraries of Material Design never reached the Production Level, which are compared with the official Angular version & the community React version (such as MUI). There are always some useful components are unfinished...

Wiz and Angular are merging, so there are parts of Wiz that are already popping up in open source likejsaction as Event Dispatch in Angular!

Angular Material and Material Web (aka Material Wiz) are two separate teams. There's still a ways to go before Wiz-Angular reaches its final form and component sets could be interchangeable, so they both need dedicated support right now.

Angular Material is working on the open source side of Google framework components, and Material Wiz has shifted its focus to the internal side of Google framework components.

🥲 🥲 🥲

That is correct, ourroadmap is out of date now, I have a task to update it. The work for 2024 is no longer planned.

The post covers more details, but expect minimum maintenance. I'll be volunteering where I can to continue to provide support.

It's not going to happen, but it's still good to hope that MWC can continue to stick around. (Disliking your leadership so much, it's sad why your leaders are putting MWC teams in Wiz frames) 🥲 🥲 🥲

Yes; Material Web Components, the project (aka MWC), refers to both<mwc-*> (pre-1.0) and<md-*> (1.0+) components. All component versions of this project are in maintenance mode.

I love Pokemon Go, it's an app. I'm so sorry you don't like apps. You're missing like half the internet.

@tomasdev touche

He's an old guard dev.

why would it be lol

a security linter is not a lit alternative

No, that's a separate 'Wiz' from Google's web framework also called Wiz

What abouthttps://github.com/angular/components?

Why should everyone use Angular?

What abouthttps://github.com/angular/components?

Why should everyone use Angular?

It's an approach, but there is another, likematerial ui.

These are fair criticisms, I understand your disappointment 😞

I feel the same way. My heart was ripped out when Polymer was stopped, as that is still my all time favorite library. At this point I don't think I will ever have confidence in anything front end from Google again. Nothing against the Polymer dev. team, though. They have been the absolute best and my favorite since they are so responsive and helpful. I guess it's Google's business or finance units that make these really bad decisions and I hope they get this feedback.

My heart was ripped out when Polymer was stopped

@dman777 I feel the same about Polymer, and I have some further thinking about these Web components libraries:https://www.zhihu.com/question/614602925/answer/3142781156

@maicol07 I'd like to join.

@bocajthomas invite sent!

@maicol07 I'd like to join. What do you think about material-web-react repo or something of that sort so that components can be easily used in React. Unfortunately, after some trying, I wasn't really able to make the lit-react generator work with this, so for the time being, custom own generator should probably be used, or react lit wrapper components can be written by hand.

@maicol07 I'd like to join. What do you think about material-web-react repo or something of that sort so that components can be easily used in React. Unfortunately, after some trying, I wasn't really able to make the lit-react generator work with this, so for the time being, custom own generator should probably be used, or react lit wrapper components can be written by hand.

Done! Unfortunately, I don't use React, I only use Vue. I've tried the Vue generator (which should be similar to the React one), but it didn't work for me. I don't think adding React wrappers should be included in the main Material Web, but should be a wrapper package instead (can be inside the org, though)

I don't think adding React wrappers should be included in the main Material Web, but should be a wrapper package instead (can be inside the org, though)

Yes, that is what I meant. There is already a React package, but with wrappers written by hand, so I think it could just be used and updated undeneath the material-web-community org. Not sure about Vue, but I think it could be in a similar style so we could have repos/packages: material-web-react, material-web-vue.

Lit is not actively maintained and has no roadmap, it is at maximum, also in "maintenance mode", without maintenance. We need to be careful with the people looking to change frontend frameworks.

Lit is actively maintained. It is stable which means new features don't often need to be introduced. That is a lot different to "maintenance mode" and "not actively maintained".

No, that is not the case. Last year Astro dropped support to lit because of the bad SSR implementation that was giving them too much work to fix issues:withastro/astro#11680

And nothing changed. It is ok if they are not actively developing the framework but it doesn't make sense to pretend it is "actively maintained".

it is indeed the case, lit is actively maintained. it was last released last month.

just because some larger pieces of work haven't been finished doesn't mean it is inactive. it is a small team so larger work doesn't move so quickly.

Could someone share some of those third-party alternatives that@taylor-vann mentioned in the post? As always with web frameworks, there are so many alternatives, it is very easy to get lost. Even in this overall discussion thread, there are so many alternatives and rewrites shared but most of them are not so good and don't look so trustworthy. I'm lost. Help!!

Yes, the same Material tokens are used across MWC, Wiz, and Angular :)

MWC and Wiz used to share even more code beyond tokens, so there's a lot of familiar pieces.

Has wiz been made publicly available yet? I can't seem to find any relevant links...

Yes, until they have maintainers.

https://io.google/2025/

That is correct, new Expressive features are not planned for MWC.

@asyncliz wouldn't be possible to update the tokens and with them allowing the community to update the components to the new designs/features?

Generating new tokens is possible (asked in#5805, I'm taking a look). Updating MWC touse the new tokens is much more difficult, since it would require effort to update and migrate internal projects as well.

Well, we're committed to continued maintenance since we still have many users of this library!

If you're instead asking for an update on if development will resume, I'm afraid I don't have any news for that 😔

But if more Google apps move to the new Material Expressive which is not support by this tool, would it still continue to be maintained?

But if more Google apps move to the new Material Expressive which is not support by this tool, would it still continue to be maintained?

The Google apps don't use this library, they're either using the internal one or the Angular Material library as far as I know.

The nuance of what "maintained" means differs for each person. To be fair though, I'm still maintaining this project 😅

Forks and different directions are always welcome in open source!

Yes, you need more than 1 person to claim it's maintained. This is also known as redundancy. People get sick, die, etc.

The repo README does not explain (neither does its configuration) whether it's a fork, a custom implementation or something else. It does not mention what standards it is coded with, accessibility, SLA, security reviews, etc.

One thing isto be able to fork it and modify it and an extremely different thing is toclaim it is maintained.

I think treeder's version is valid. It is literally maintained, as to update the code and plan for the future (both occurring: he's been making bug fixes, simplifications, and a task list for free) is to maintain. It may have abus factor of 1 - you can change that by helping maintain it or bringing it to a state of relevance where others maintain it. Complaining about how nobody has helped yet isn't helpful.

I hope treeder will make it an actual fork (instead of its current state where it has no attribution: it's cut off from the network and all previous history is collapsed into one commit) though.

Yes, you need more than 1 person to claim it's maintained. This is also known as redundancy. People get sick, die, etc.

There are tons (if not most) open source projects that are built/maintained by a single person. "People get sick, die, etc." It's open source, fork it and maintain it yourself. And if you'd prefer redundancy, then contribute to it.

The repo README does not explain (neither does its configuration) whether it's a fork, a custom implementation or something else. It does not mention what standards it is coded with, accessibility, SLA, security reviews, etc.

Literally the second paragraph:

One thing isto be able to fork it and modify it and an extremely different thing is toclaim it is maintained.

There's new components, bug fixes, etc. Not sure what you're definition is, but I'd say that's it.