❗MWC is in maintenance mode

[asyncLiz]

Hi everyone, we have an important update for the community.

Material Design is focusing on support for Google's large-scale internal Wiz framework, and has reassigned the engineers working on Material Web Components. This places MWC into maintenance mode.

MWC is not deprecated or going away, but Material Design is no longer actively staffing its development.

What does this mean?

• New features and components are no longer planned.
• GitHub PRs will not be accepted by default. Small PRs may be reviewed on a case-by-case basis.
• Ongoing support will require volunteer time from the team.

We are investigating ways to continue development of new features and components, including identifying new maintainers. We'll post updates here as we learn more.

Thank you,

Elizabeth, on behalf of the Material Web team

[asyncLiz]

I know this change is discouraging to many, but it does not diminish our pride in what Material Web Components and the team have accomplished! Here are a few unforgettable milestones we want to celebrate: ☺️

• 🥇 First implementation of Material 3 for the web!
• 📈 4 million downloads from npm! (200,000+ per month!)
• 📈 1 million downloads per month from jsdelivr!
• 🎉 Used in over 150 Google projects!
• ♿ Fully tested for accessibility!
• 🚀 Trailblazing standards: popover, ElementInternals, Accessibility Object Model, CSS layers, and more!
• 🎨 Web resources on material.io!
• 🔧 Live demos and docs on material-web.dev! (and fully server-side rendered!)

Big cheers to Elliott, Dan, Steve, and Andrew (and me!) for the amazing work and passion they've given to this project. ♥️

While the path ahead is uncertain, I'm excited to see what we will build together as the project continues to evolve with the support of this amazing community.

Elizabeth

[abdonrd]

Thanks to all the team!

[Darrenbydesign]

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 🙏🏾

[vicentematus]

This project looks really promising, especially pushing Web Components as a standard on one of the biggest UI libraries. But, it's a shame that for whatever internal reasons Google decided to put a pause on it. I hope Google let you guys come back soon to the project and not leave it on the dust.

[mreiche]

Let’s see on Google Graveyard 😓

[kuncevic]

We still have that https://github.com/material-components/material-components-web right? 🤔

[asyncLiz]

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 is not 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.

[jensborch]

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?

[asyncLiz]

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 a couple of comments in this discussion that offer more insights on Angular, but the best place to ask would be on the Angular components GitHub repo.

[kuncevic]

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

[zdhxiong]

If you need an alternative, you can try using mdui. It is also based on Material 3 and Web components.
https://github.com/zdhxiong/mdui

[mreiche]

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

[shadow-identity]

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

[zdhxiong]

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.

[jogibear9988]

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.

[TechQuery]

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

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

[anlexN]

material-web is drived by google company not by community.

For example, this dicussion.

I understand many source code and am a google contributor.

So I recommand:

1. understand more soure code so that update those to satisfy your requirements.
2. learn more UI framework, like fluentio, not just only material design.
3. material-web team must listen more to community, not just only google company plan.

I do not say whether material-web is right or wrong, I do say the fact.

[datvm]

[mreiche]

See above (mdui).

[43081j]

fwiw 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.

the team has done great work making some of the cleanest web components i've seen. sad to see them move to other projects but sure we'll cross paths still and eventually get back to this.

awesome work to you all 🙏 every dev i've mentored over the years on WCs has learnt from this repo and the old one.

[asyncLiz]

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

[TechQuery]

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...

[shadow-identity]

Thank you guys for making it real, and also thank you for the announcement.
I hope google will bring you back to the project, we relied heavily on it when choosing an UI library.

[zb3]

Google's large-scale internal Wiz framework

Ouch.. I hope Google will one day open source that one, even it it was only for entertainment purposes :)

[asyncLiz]

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

[siegenthalerroger]

As the Wiz and Angular teams are being combined, can one assume that the focus on angular-material will increase as well? Or what is the relation between angular-material and the internal wiz-angular components?

[asyncLiz]

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.

[jeffwklein]

Bummer news, I'd found the icon library incredibly useful for our work here at the internet archive, and we are excited to adopt more of these. I'd offer to help maintain but we are already quite resource-scarce.

[asyncLiz]

🥲 🥲 🥲

[anlexN]

combination is correct.

1. If your theory is good, it is good for every company, team, framework.
2. Future is belong to open, transparent, standard company.
3. Smart people is the only core of the company. Open source is not only open souce code, but also cultivate smart people. It is very big help for a company to hire smart peoples. I am also smart people.
4. Trade and technological barriers have been increased and deepened. Open source is not subject to these restrictions.

I learn knowledge from Adobe, Amazon, Google, IETF, Microsoft and more. I like to compare those knowledge and shape one knowlege that is good for me. Only by comparison can I discover, Only by comparison can I master.

[motss]

Well, it's dead. Let's move away from Material Design, for web at least.

[gkj17]

Does it mean that a feature that was intended to be developed this year can't be developed now?It's tough, but I'm still sure you guys will continue to maintain it afterward right?

[asyncLiz]

That is correct, our roadmap 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.

[gkj17]

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) 🥲 🥲 🥲

[YieldRay]

I created a hobby component library for myself. Previously I believed that MWC was the finest implementation, given the extensive community implementation I've seen.
I still think MD3 deserves to be implemented for the web. It’s disappointing to see such an announcement, especially since many components remain unimplemented.

[sandeshpd]

So is this project abandoned since there seems almost no updates about it?

[asyncLiz]

It's still in maintenance mode right now, which means you shouldn't expect many (if any) updates outside of contributions and security patches.

[neoacevedo]

It's still in maintenance mode right now, which means you shouldn't expect many (if any) updates outside of contributions and security patches.

In short words: abandoned. This repo then should be marked as read-only to don't make people lose their time doing pull requests or opening new issues that won't be anymore reviewed nor answered.

[tomasdev]

In short words: abandoned. This repo then should be marked as read-only to don't make people lose their time doing pull requests or opening new issues that won't be anymore reviewed nor answered.

There's a distinction between "maintenance" and "abandoned." As stated, they're looking for maintainers, so pull-requests are probably appreciated even if not immediately taken action on.

Give the team some slack.

[dman777]

I am bit confused... I understand that MWC is in maintenance mode. But MWC components are not MD components. For example, mwc-button is not the same as md-button. Are the MD components also in maintenance mode?

[asyncLiz]

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.

[ronnievsmith]

Gemini said: *Here's a simple way to think about it:* - *Flutter:* Learn one framework, build for multiple platforms. Potentially faster development, good performance. - *Material Components (Android):* Focus on a single platform, deeper integration with Android. Requires Java/Kotlin knowledge. So, my recommendation would be to *avoid wasting time on proprietary stuff*. Stick with standards, namely, the Web suite (HTML/CSS/JavaScript). This falls under the umbrella of the KISS doctrine, or always avoid over-engineering things. Remember, Microsoft, Apple, Google, ...they are in *business*. Where there is mystery, there is margin. The World Wide Web is the proper platform for 99.999% of all user interfaces. Nobody likes "apps". Go build something for the client so ubiquitous that it's referred to as 'clientless' - the Web browser.

…

On Sun, Jan 26, 2025 at 3:44 PM Darin Hensley ***@***.***> wrote: I am bit confused... I understand that MWC is in maintenance mode. But MWC components are not MD components. For example, mwc-button is not the same as md-button. Are the MD components also in maintenance mode? — Reply to this email directly, view it on GitHub <#5642 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADBJF66DOYZL7NRHOWADPF32MVJLHAVCNFSM6AAAAABJDBEODGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOJWGIZDKMI> . You are receiving this because you were mentioned.Message ID: <material-components/material-web/repo-discussions/5642/comments/11962251@ github.com>

[tomasdev]

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

[neoacevedo]

@tomasdev touche

[neoacevedo]

He's an old guard dev.

[ncouture]

@asyncLiz Is this related to the acquisition of Wiz.io by Google?

[KTibow]

why would it be lol

a security linter is not a lit alternative

[asyncLiz]

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

[rj33]

It is hard to trust any Google material design web implementation now. They all seem to end up sleeping with the fishes well before reaching completion.

I started with MDL. They killed that.
I moved to MDC. They killed that.
I was considering moving to MWC, but they've killed that. Yes technically 'in maintenance' not dead, but given there is no more development planned, and the unimplemented features still on the now-dead roadmap, it is effectively dead.

I'm tired of hopping from one murdered google MD project to the next. I'll be choosing a third party implementation for my next UI rewrite. The risks of a small part-time open source development team backing your MD library choice seems to be FAR lower than the risk of relying on Google to produce a stable MD platform. Especially one that is complete and tracks MD version updates over time rather than requiring a complete hop from one incompatible framework to the next. Currently evaluating beercss. Probably not perfect, but have a lot more faith in it being actively maintained in a few years time than anything Google will ever produce in this space.

Very disappointing. I feel sorry for the Google people that were working on these projects. I'm sure they hoped for much more , and it is not their fault Google suffers from such rapid attention switches.

[TechQuery]

What about https://github.com/angular/components?

Why should everyone use Angular?

[neoacevedo]

What about https://github.com/angular/components?

Why should everyone use Angular?

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

[asyncLiz]

These are fair criticisms, I understand your disappointment 😞

[dman777]

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.

[TechQuery]

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 hope new maintainers will be found soon! In the meantime, I'll continue maintaining and supporting (although slowly) Material Web Additions, an additional set of components for Material Web (using the same structure and design of Material Web). Recently, I've pushed v1.6.0 that adds the M3 snackbar component, although I hope someday we'll be able to see an official implementation!

[bocajthomas]

If you'd like to help just send a PR and I'll be happy to review it!

Will do, I am a bit busy with other projects, once i get some free time.

[bocajthomas]

@maicol07 👀👀
Still a work in progress, but its getting there
https://bocajthomas.github.io/Material3-Web-Expressive/

Recording.2025-06-10.143214.mp4

/**
 * A Material 3 - Web Expressive | Split Button component. 
 * Developed by bocajthomas
 * Copyright (c) 2025 bocajthomas
 *
 * 
 * The SplitButton component displays a primary action button and a secondary menu button.
 * 
 * @example
 * <!-- Usage in HTML -->
 * <md-split-button></md-split-button>
 * 
 * @fires main-click - Dispatched when the main button is clicked.
 * @fires menu-click - Dispatched when the menu button is clicked.
 * 
 * @slot - (Not used) The component does not currently support slots.
 * 
 * @csspart md-split-button - The container of the split button.
 * @csspart common-button - The main action button.
 * @csspart menu-icon-button - The menu icon button.
 * 
 * @cssprop --md-sys-color-surface - Background color of the button.
 * @cssprop --md-sys-color-outline-variant - Border color of the button.
 * @cssprop --md-sys-color-surface-variant - Hover background color.
 */
class SplitButton extends HTMLElement {
    constructor() {
        super();
        const shadow = this.attachShadow({ mode: 'open' });

        const newLocal = `
            <link href="https://fonts.googleapis.com/icon?family=Material+Icons+Round" rel="stylesheet">
            <style>
            :host {
                display: inline-block;
                font-family: 'Roboto', sans-serif;
                font-size: 14px;
                cursor: pointer;
                position: relative;
                user-select: none;
                padding: 0;
            }
            .md-split-button {
                display: flex;
                align-items: center;
                justify-content: center;
                color: white;
                cursor: pointer;
                gap: 2px;
            }

            .material-icons-round {
                font-size: 20px;
            }

            .common-button {
                align-items: center;
                justify-content: center;
                display: flex;
                padding: 20px;
                background-color: rgb(0, 0, 0);
                border-bottom-left-radius: 30px;
                border-top-left-radius: 30px;
                border-bottom-right-radius: 10px;
                border-top-right-radius: 10px;
                gap: 10px;
            }

            .menu-icon-button {
                align-items: center;
                justify-content: center;
                display: flex;
                padding: 20px;
                background-color: rgb(0, 0, 0);
                border-bottom-left-radius: 10px;
                border-top-left-radius: 10px;
                border-bottom-right-radius: 30px;
                border-top-right-radius: 30px;
                transition: border-bottom-left-radius 0.1s ease-in-out, border-top-left-radius 0.1s ease-in-out;
            }

            .expanded {
                border-bottom-left-radius: 30px;
                border-top-left-radius: 30px;
                border-bottom-right-radius: 30px;
                border-top-right-radius: 30px;
            }

            .menu-icon-button .material-icons-round {
                transition: transform 0.1s ease-in-out;
            }
            </style>
            
            <div class="md-split-button">
                <div class="common-button" tabindex="0">
                    <span class="material-icons-round">edit</span>
                    <span class="label">Edit</span>
                </div>

                <div class="menu-icon-button" tabindex="0" aria-haspopup="true" aria-expanded="false">
                    <span class="material-icons-round">expand_more</span>
                </div>
            </div>
        `;
        shadow.innerHTML = newLocal;

        this._mainButton = shadow.querySelector('.common-button');
        this._menuButton = shadow.querySelector('.menu-icon-button');
        this._menuIcon = shadow.querySelector('.menu-icon-button .material-icons-round');

        const updateIcon = () => {
            const icon = getComputedStyle(this).getPropertyValue('--md-split-button-icon').trim();
            if (icon) {
                const iconSpan = this._mainButton.querySelector('.material-icons-round');
                if (iconSpan) iconSpan.textContent = icon;
            }
        };
        updateIcon();

        const observer = new MutationObserver(() => updateIcon());
        observer.observe(this, { attributes: true, attributeFilter: ['style'] });

        this._mainButton.addEventListener('click', () => {
            this.dispatchEvent(new CustomEvent('main-click', { bubbles: true, composed: true }));
        });

        this._menuButton.addEventListener('click', () => {
            this.dispatchEvent(new CustomEvent('menu-click', { 
                bubbles: true, 
                composed: true 
            }));
            this._menuButton.classList.toggle('expanded');
            this._menuIcon.style.transform = this._menuButton.classList.contains('expanded') ? 'rotate(180deg)' : 'rotate(0deg)';
        });
    }
}

customElements.define('md-split-button', SplitButton);

[maicol07]

Wow, great! I'd like (not very soon, busy with other things atm) to fork Material Web and call it "Material Web Community Edition" (something like Materialize Community did: https://github.com/materializecss/materialize) with different branches per component/major change, also compatible with the original repo (this one) to send a PR. Also, a main branch with all the changes done (so it can be published). This way we are covered in both cases:

• M3 web (original repo) will be maintained
• M3 web will be discontinued/deprecated

Now that I think about it, we need to figure out how to get updated tokens if we don't get updated ones (I think maybe by scraping the M3 website)

[TechQuery]

/**
 * A Material 3 - Web Expressive | Split Button component. 
 * Developed by bocajthomas
 * Copyright (c) 2025 bocajthomas
 *
 * 
 * The SplitButton component displays a primary action button and a secondary menu button.
 * 
 * @example
 * <!-- Usage in HTML -->
 * <md-split-button></md-split-button>
 * 
 * @fires main-click - Dispatched when the main button is clicked.
 * @fires menu-click - Dispatched when the menu button is clicked.
 * 
 * @slot - (Not used) The component does not currently support slots.
 * 
 * @csspart md-split-button - The container of the split button.
 * @csspart common-button - The main action button.
 * @csspart menu-icon-button - The menu icon button.
 * 
 * @cssprop --md-sys-color-surface - Background color of the button.
 * @cssprop --md-sys-color-outline-variant - Border color of the button.
 * @cssprop --md-sys-color-surface-variant - Hover background color.
 */
class SplitButton extends HTMLElement {
    constructor() {
        super();
        const shadow = this.attachShadow({ mode: 'open' });

        const newLocal = `
            <link href="https://fonts.googleapis.com/icon?family=Material+Icons+Round" rel="stylesheet">
            <style>
            :host {
                display: inline-block;
                font-family: 'Roboto', sans-serif;
                font-size: 14px;
                cursor: pointer;
                position: relative;
                user-select: none;
                padding: 0;
            }
            .md-split-button {
                display: flex;
                align-items: center;
                justify-content: center;
                color: white;
                cursor: pointer;
                gap: 2px;
            }

            .material-icons-round {
                font-size: 20px;
            }

            .common-button {
                align-items: center;
                justify-content: center;
                display: flex;
                padding: 20px;
                background-color: rgb(0, 0, 0);
                border-bottom-left-radius: 30px;
                border-top-left-radius: 30px;
                border-bottom-right-radius: 10px;
                border-top-right-radius: 10px;
                gap: 10px;
            }

            .menu-icon-button {
                align-items: center;
                justify-content: center;
                display: flex;
                padding: 20px;
                background-color: rgb(0, 0, 0);
                border-bottom-left-radius: 10px;
                border-top-left-radius: 10px;
                border-bottom-right-radius: 30px;
                border-top-right-radius: 30px;
                transition: border-bottom-left-radius 0.1s ease-in-out, border-top-left-radius 0.1s ease-in-out;
            }

            .expanded {
                border-bottom-left-radius: 30px;
                border-top-left-radius: 30px;
                border-bottom-right-radius: 30px;
                border-top-right-radius: 30px;
            }

            .menu-icon-button .material-icons-round {
                transition: transform 0.1s ease-in-out;
            }
            </style>
            
            <div class="md-split-button">
                <div class="common-button" tabindex="0">
                    <span class="material-icons-round">edit</span>
                    <span class="label">Edit</span>
                </div>

                <div class="menu-icon-button" tabindex="0" aria-haspopup="true" aria-expanded="false">
                    <span class="material-icons-round">expand_more</span>
                </div>
            </div>
        `;
        shadow.innerHTML = newLocal;

        this._mainButton = shadow.querySelector('.common-button');
        this._menuButton = shadow.querySelector('.menu-icon-button');
        this._menuIcon = shadow.querySelector('.menu-icon-button .material-icons-round');

        const updateIcon = () => {
            const icon = getComputedStyle(this).getPropertyValue('--md-split-button-icon').trim();
            if (icon) {
                const iconSpan = this._mainButton.querySelector('.material-icons-round');
                if (iconSpan) iconSpan.textContent = icon;
            }
        };
        updateIcon();

        const observer = new MutationObserver(() => updateIcon());
        observer.observe(this, { attributes: true, attributeFilter: ['style'] });

        this._mainButton.addEventListener('click', () => {
            this.dispatchEvent(new CustomEvent('main-click', { bubbles: true, composed: true }));
        });

        this._menuButton.addEventListener('click', () => {
            this.dispatchEvent(new CustomEvent('menu-click', { 
                bubbles: true, 
                composed: true 
            }));
            this._menuButton.classList.toggle('expanded');
            this._menuIcon.style.transform = this._menuButton.classList.contains('expanded') ? 'rotate(180deg)' : 'rotate(0deg)';
        });
    }
}

customElements.define('md-split-button', SplitButton);

@bocajthomas TSX may be a better DSL for such long HTML:
https://github.com/EasyWebApp/DOM-Renderer

[bocajthomas]

@bocajthomas TSX may be a better DSL for such long HTML: https://github.com/EasyWebApp/DOM-Renderer

I am ok with the current set up, but thanks anyways

[ronnievsmith]

Google is pushing Flutter now. Google is a corporation that must answer to investors. The Web is the undisputed KING of UI. Nobody prefers to "install an app" [flutter]. I'll circle back in a couple of years with another reminder.

…

On Mon, Apr 7, 2025 at 12:35 PM Maicol Battistini ***@***.***> wrote: I hope new maintainers will be found soon! In the meantime, I'll continue maintaining and supporting (although slowly) Material Web Additions <https://material-web-additions.maicol07.it/>, an additional set of components for Material Web (using the same structure and design of Material Web). Recently, I've pushed v1.6.0 <https://github.com/maicol07/material-web-additions/releases/tag/v1.6.0> that adds the M3 snackbar component, although I hope someday we'll be able to see an official implementation! — Reply to this email directly, view it on GitHub <#5642 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADBJF6Z4MLJDOODEDSSL6ZT2YKZPNAVCNFSM6AAAAABJDBEODGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENZVGQZTEMI> . You are receiving this because you were mentioned.Message ID: <material-components/material-web/repo-discussions/5642/comments/12754321@ github.com>

[taylor-vann]

Unfortunately this isn't a google graveyard incident. As a former engineer on the Material Web team (m2 & m3), I can confirm this "deprecation" was completely self inflicted.

IMHO Materal Web (m3 specifically) was an objective failure. We were dog-walked by almost every third-party alternative! But sometimes we fail and that's okay. In the process, we had the privilege to learn / experience the incredible challenges of deploying a component set to one of the world's largest monorepos.

We deployed sub optimal implementations years late that no one wanted to use and no one could recommend. And if you've tried to use these components, you probably understand where I'm coming from. Pretty easy decision from the higher ups at that point.

I still believe web components provide amazing quality-of-life improvements for developers and the web in general. And I think we (Material Web, Lit specifically) were an fantastic set of engineers. I'm excited to see what my former coworkers do in the future. But ultimately we were unheard, under-utilized, and some of us were eventually un-hired.

I would use a different strategy in future component sets. Both as a team and an implementation.
But I can't in good conscious let this one slide into the google graveyard. The value of what we learned far outweighs the chagrin of our failure. And we should share that knowledge. Might make a good blog post. Will post if it gets there.

<3 miss y'all

[43081j]

On a side note, I feel like Lit is not alive anymore ether

FYI this is certainly not true. Lit is actively maintained. Just because a project doesn't change much doesn't mean it is dead, code can become stable and that is a good thing.

We should be careful saying things like this as it may steer people away from an active project.

[meiraleal]

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.

[43081j]

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".

[meiraleal]

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".

[43081j]

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.

[WalkQuackBack]

I've been poking around Google's Wiz framework and the components being rolled out for quite a while, and wanted to ask: is GM3 the aforementioned Wiz version of MWC?

They seem to share identical CSS variables aside from the prefix, the focus layer and ripples are the same, and there's components there like colour pickers, segmented buttons, and navigation that seem to follow a similar technical structure to the one seem here.

[asyncLiz]

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.

[gkj17]

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

[cosmicallyrun]

So Material 3 Expressive won't be implemented, right?

[bocajthomas]

Yes, until they have maintainers.

[vdegenne]

https://io.google/2025/

[asyncLiz]

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

[maicol07]

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

[asyncLiz]

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

[for-the-zero]

a year pasted
could the maintenance mode be ended

[asyncLiz]

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 😔

[mflamentj2s]

I recently use that library for a project without framework. It is pretty nice to use and very flexible.
It could be a tool that spreads a large use of material.
Hope the project will restart soon, the good timing to do it is now and the project could be overtaken by futur other libraries.
Nice job anyway, I expect a happy ending.

[treeder]

FYI, for those that are looking for a maintained version of this, we have one here:

https://github.com/treeder/material

[asyncLiz]

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!

[tomasdev]

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 is to be able to fork it and modify it and an extremely different thing is to claim it is maintained.

[KTibow]

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 a bus 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.

[treeder]

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 is to be able to fork it and modify it and an extremely different thing is to claim it is maintained.

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

[tomasdev]

@treeder is in his full right to fork. I question the value of promoting such fork here under a claim of maintenance, where this discussion literally asked for maintainers for this repo. At this point this conversation is counter-productive for all of us.