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

[vdegenne]

unfollowed (lol)

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

[anlexN]

No, @bastiW @JhorAVi you have very big misunderstand to me. Because I just want to say some people in this discussion have same problems that I also was in trouble some years ago. I just wonder how much old those peoples are. This is not about polite problem

[maicol07]

If you end up following the maintainers way, I'll candidate! 🙋🏻‍♂️

[DRiFTy17]

If anyone is looking for an alternative web component library that is based on Material, check out Tyler Forge™ components or view the repo here. This library originally derived directly from material-components-web (MDC), and has also taken inspiration from MWC and the great work being done in both of these projects. While it no longer uses MDC due to it being deprecated, it implements Material (mixture of M2 and M3), should feel very familiar, and is very actively maintained and will continue to be.

[caraya]

@asyncLiz

Is there a way to mentor people who want to help keep the project afloat? I understand that material components is out of scope for the team's new assignment, but it would be nice to be able to keep the project moving and have people who can review PRs and approve changes

[asyncLiz]

The best way to get started is to join the lit.dev/discord server and hop into the #material channel to chat with us and learn more about where folks can help out.

[ronnievsmith]

The idea of favoring custom elements over native HTML elements remains Dead On Arrival (DOA). M3-Web is an over-engineered bridge to nowhere.

[caraya]

The idea of favoring custom elements over native HTML elements remains Dead On Arrival (DOA). M3-Web is an over-engineered bridge to nowhere.

Then why are you commenting in a forum supporting a technology that you consider DOA? What's your angle? Why start discussion in a forum dedicated to a dead technology?

[ronnievsmith]

Google needs a mature and seasoned software architect to get it done. Younger enthusiastic coders tend to veer off in the weeds, as happened here with the M3-Web *JavaScript *library. *Material Design is* an adaptable system of guidelines, components, and

tools that support the *best practices of user interface design*.

Going backwards happens sometimes. Material Design Lite remains the high water mark so far. https://github.com/google/material-design-lite

…

On Fri, Jul 19, 2024 at 3:24 PM Carlos Araya ***@***.***> wrote: The idea of favoring custom elements over native HTML elements remains Dead On Arrival (DOA). M3-Web is an over-engineered bridge to nowhere. Then why are you commenting in a forum supporting a technology that you consider DOA? What's your angle? Why start discussion in a forum dedicated to a dead technology? — Reply to this email directly, view it on GitHub <#5642 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADBJF6375ZSMGPSXB72FDCTZNFYZBAVCNFSM6AAAAABJDBEODGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMBZHEYDGMY> . You are receiving this because you commented.Message ID: <material-components/material-web/repo-discussions/5642/comments/10099033@ github.com>

-- Ronnie Royston (504) 460-1592

[TechQuery]

@ronnieroyston https://web-cell.dev/ (My Web components engine) wrapped MDL, MDC & MW (https://github.com/EasyWebApp/Material-Cell), I'm too tired to follow Google's refactoring, why the proposal author company Google can not release a stable Web components library for its own Material Design?

[gobijan]

I kind of like beercss for its simplicity. It's super simple to implement and you get quick results without over engineering material 3.

[KTibow]

Let's list them.

• Dialog
  Can't close with ESC, and doesn't lock focus to within itself
• Extended FAB
  Non-standard behavior of showing text only on hover
• Progress
  In both bar and circular, the end isn't rounded
• Search
  Bugged, you can't type anything as you lose focus as soon as you try
• Text input
  Missing text cursor in edges (admittedly official material libs did this previously so)
• Slider
  Missing click/drag cursor
  Incorrect rounding of handle
  Handle stays "active" until you click somewhere else
• Probably more stuff I didn't check, such as spacing anomalies
• General: Elements like navigation rail, drawer, list, icon button, etc
  Non-standard behavior of handling hover by showing items as selected instead of hovered
• General: fonts
  Roboto isn't loaded
  Letter spacing doesn't change by font location
• General: interactivity
  Elevation effect is too simple
  No transitions in many places
  Between pressing your mouse and releasing your mouse, the ripple disappears
  The ripple (including hover/focus states) is a fixed color
  The ripple always comes from the center
  Some things are clickable but aren't buttons (bad for accessibility)
  No focus outline (bad for accessibility)
• General: shapes
  Endorses a lot of non-standard stuff, like odd rounding of elements, changing the background or outline of a component, using more blur and shadows, etc

I also implemented Material 3, so although my experience gives me a clearer understanding of what's expected, it creates a bit of a conflict of interest

[gobijan]

Oh wow, I had a look at your Svelte-based implementation. Do you think you could contribute to BeerCSS with your knowledge and implementation experience? I use BeerCSS for my Ruby on Rails application, Sunnybox.io. For example, in my case, I need something more like Bootstrap (which BeerCSS is similar to) rather than a Svelte or React-specific library and I think same goes for many others.

[KTibow]

BeerCSS is interesting, and it seems useful for creating a website where you would want to use completely premade things and minimal JS, but it's not really my thing. Most of my personal projects are highly interactive and benefit from using Svelte.

Admittedly I could try to solve some of these problems. However, I don't use it so I'm not familiar with it and wouldn't get any benefit from improving it. And other problems are just because of its architecture, which isn't my place to restructure.

[gobijan]

Fair. I will copy your findings over to their issue tracker and try to look into it when I find the time.

[laurentpayot]

+1 for Beercss. MWC was much too big for my use case so I used Beercss and honestly I didn’t notice the minor differences listed. Thanks to purgecss, the total Beercss CSS of my PWA is 7.8KB brotli compressed. My Lighthouse score loves it.

[fvcoder]

???

[TechAssistance]

Yet another google graveyard. Disappointing that web components were left for dead / done last, feels like they could have been completed if they were made priority, which in my mind makes more sense as PWA's are by far more common than say flutter (my personal opinion).

08/2024 (2 months post kill) and we still want this to be revived. 🙏

[KTibow]

FYI it's been requested already codyogden/killedbygoogle#1532

[TechAssistance]

oof o7

[sirkadirov]

Total shame for Google. Again and again, killing good things. Glad that I didn't use it in my projects.

[ice6]

woo, thank you for the notification. just gonna to invest some time to learn it. :)

it seems that mui is more promising, 'cause they make money from it.

so material design is not in maintain mode, just this web implementation is in maintain mode, right?

[shadow-identity]

Sadly mui sucks by design. And it is bind with React, so too far behind MWC in terms of performance.

[ice6]

thanks for your reminder. I will figure it out.

[adil-94]

Hi Team,
When can we expect other components like Card, Carousel, Select?

[Darrenbydesign]

Since this is maintenance mode I'd expect not till Google adds team members back on the project

[fvcoder]

Another alternative would be to fork this project and work exclusively with the community, following the concepts of Material Design.

[shadow-identity]

BTW they still work on this project and issuing releases, which is great and I am very grateful to the guys.

[clementmas]

It’s a shame. It reminds me of Material Design Lite. I used it a lot until I had to migrate everything away.

[willemtoerien]

Thank you to the team for building these components. I have learned a tremendous amount about web components. I have decided to build my own web components. I first started with Lit, but eventually decided to use Angular's ShadowDom encapsulation as I am mainly building angular apps and will look into it in the future for Lit (maybe). You can find it here[1].

I've added most of the components (mainly the ones I need for my projects). So, feel free to use as you wish, though I prefer you contribute to help or make suggestions. 😊 Please excuse me if it is a bit of a mess, I'm still quite a newbie on web development and it's still in its early stages. When it is a bit more stable, I'll add some documentation to it. I have also added some tailwind configurations. There is a demo project that I built showcasing each component and their settings (see video).

Some of the components I have built:

• Accordion
• Avatar
• Badge
• Breadcrumb
• Button (all variants)
• Card
• Check
  • Checkbox
  • Radio button
  • Switch
• Chip
• Date picker (embedded, modal, field)
• Dialog
• Divider
• Dropdown
• Elevation
• Fab
• Field
• Focus ring
• icon
• Icon button
• List
• Menu
• Navigation (item, embedded & sheet)
• Pin
• Popover
• Progress indicator (both variants)
• Ripple
• Segmented button
• Sheet (embedded & modal)
• Snack bar
• Tabs
• Text field
• Time Picker
• Tooltip
• Type scale

The things I haven't yet built:

• Component properties (Since I am using tailwind and ::part(), I haven't had much need for these at the moment.)
• Aria properties
• Carousel
• Slider
• App bars

[1]
https://github.com/wtprograms/material-design

m3.mp4

[wencan]

If you are unable to locate the maintainers of this project, what will be the fate of this project?
How many projects within Google rely on this project?

[vdegenne]

Adoption relies on Users too.