When is Material Web 3 Coming?

[reeceatkinson]

I would like to build a new app but am waiting on the update is there any idea when it will come?

[christophe-g]

And, this time, please do not just answer "The components are being actively worked on" and close the issue.

The community request for some kind of plan/timetable/outline (https://github.com/material-components/material-web/issues/2441#issuecomment-868359777, #3019, #2925, https://github.com/material-components/material-web/issues/386#issuecomment-800431284, and many more) is not extravagant after 3 years and 8 months and still quite a few missing components (chips, tooltip, card, ...).

I struggle to understand how the pace of development can be so slow, especially when I recall how paper-elements were released in a just couple of months (and it was the first implementation of material design, and lit was not there), and the level of communication so poor.

Sorry for the tone, but I am upset and I doubt I am the only one.

[jbingham]

Thanks for your patience and your interest! The Material Web team is targeting late 2022 for a public release of a Material 3 component set. We will be releasing components to github over the course of the year, as they're implemented.

If you recall, Material 3 was announced at Google I/O in May 2021. The Android components for Material 3 were released at Android DevSummit in late Oct 2021. The Web version is coming next.

The Material Web team's first priority has been to make sure we have a complete Material 3 component set for use by Google products. Many of those use internal web frameworks, and it's a big change for them to adopt a web components implementation based on Lit. The good news is that we're wrapping up the internal-only work, and are shifting our focus to making Material 3 web components that can be used by everyone. That's our major goal for the year.

[TKDev7]

@jbingham Jon I am kind of confused between material-web-components and material-web. Which one to choose?

[jbingham]

You're not alone!

material-components-web is our Material 2 implementation, available today. It will not be updated for Material 3. material-web will be the Material 3 implementation. It's in progress and will launch in late 2022.

Our goal is for material-web to be a long-term supported library that supports M3 and future design refreshes as well.

[yaraju]

@jbingham That's great news!

My understanding of the major difference between the two is this:

material-components-web as it is today, provides CSS styling, SASS rules and JS behaviour that can be applied to the basic html elements (label, button, etc.) However, it doesn't encapsulate style and behavior, and therefore requires framework wrappers that in turn provide that encapsulation, especially when used alongside other web UI frameworks (like Angular, React, etc.)

material-web, on the other hand, provides web components with consistent CSS/JS style/behaviour encapsulation, and can be easily dropped in aside any other framework's web components and just work without conflicts, while at the same time being customisable and extensible for advanced needs through composition, or custom theming. (This would also mean no more need for framework wrappers anymore!)

I'm really glad to hear that the Material Team's focus is on the latter (material-web), for both Material 3 as well as long-term support and future refreshes!

[christophe-g]

Thanks a lot for the answer @jbingham , this is appreciated.

What I hear behind the lines however is not very encouraging.

But I might hear wrong, so please correct me:

• md2 is never going to be finalized nor completed (even simple components that were clearly on the pipeline at some stage and that consumer of the library trusted)
• The open bugs on md2 is not going to be worked on, even important issues like RTL not supported, accessibility testing not integrated, no decision on how anchor-able component work, just to name a few.
• md3 component is a full rewrite
• md3 component is a full rewrite with a team newly exposed to lit (hence I suppose newly exposed to web components)

I know what I sign for with Beta libraries, mostly a rough ride and a lot of breaking changes along the way and this is o.k.. Here, we have something different: Promises not kept, even years after.

Someone said it clearly in one of the comments (https://github.com/material-components/material-web/issues/386#issuecomment-799393845):

It is assumed that the value proposition of web components and for which several of us have based our projects on LitElements is due to the promise of a roadmap that was made since 2020 with the web components that are yet to be developed.

[reeceatkinson]

Right! So when the material 3 ui is done will it be at m3.material.io

[maicol07]

@jbingham I'm very interested to the new M3 components! Maybe if you give us some instructions on how to use them we can test them and report issues to the Material team. Like a pre-alpha release

[jbingham]

@maicol07 You can track progress in https://github.com/material-components/material-web/tree/master/components

There's not yet a build process, so it's mostly just for following along on progress.

[asyncliz]

Heya folks! We've gotten some questions on when Material 3's components will be available to consume on npm. I wanted to drop an update and let you all know that I'll be working on this next week so you can follow along as an early adopter!

[hello-smile6]

Heya folks! We've gotten some questions on when Material 3's components will be available to consume on npm. I wanted to drop an update and let you all know that I'll be working on this next week so you can follow along as an early adopter!

When will I be able to import modules from jsdelivr?Just realized it works with ?module from unpkg, going to try buttons now.

[hello-smile6]

working on this next week

So, is @material/web going public next week?

[hello-smile6]

Heya folks! We've gotten some questions on when Material 3's components will be available to consume on npm. I wanted to drop an update and let you all know that I'll be working on this next week so you can follow along as an early adopter!

~When will I be able to import modules from jsdelivr?~Just realized it works with ?module from unpkg, going to try buttons now.

Works perfectly!

[asyncliz]

working on this next week

So, is @material/web going public next week?

I'm gonna be working on it... whether or not I finish it in a single sprint is up to my mental health 😅

[reeceatkinson]

working on this next week

So, is @material/web going public next week?

I'm gonna be working on it... whether or not I finish it in a single sprint is up to my mental health 😅

Yes! Will be implementing the moment it goes live...

[hello-smile6]

working on this next week

So, is @material/web going public next week?

I'm gonna be working on it... whether or not I finish it in a single sprint is up to my mental health 😅

Will it be possible to use it from unpkg?

[reeceatkinson]

working on this next week

So, is @material/web going public next week?

I'm gonna be working on it... whether or not I finish it in a single sprint is up to my mental health 😅

Also will it be avaliable at https://m3.material.io/

[asyncliz]

Will it be possible to use it from unpkg?

Yes!

Also will it be avaliable at https://m3.material.io/

I don't believe so, but material.io is a separate team so I don't know what they have planned.

[hello-smile6]

Will it be possible to use it from unpkg?

Yes!

Also will it be avaliable at https://m3.material.io/

I don't believe so, but material.io is a separate team so I don't know what they have planned.

So, will I just import the @material/web package 2 weeks from now and have everything work without any configuration?

[reeceatkinson]

Will it be possible to use it from unpkg?

Yes!

Also will it be avaliable at m3.material.io

I don't believe so, but material.io is a separate team so I don't know what they have planned.

@asyncLiz Where will the docs be then? material.io or m3.material.io

[treeder]

@reeceatkinson I'd assume the docs will be right here in this repo where they belong.

[asyncliz]

The developer documentation will be in this repository with READMEs. The design documentation will be on m3.material.io

[reeceatkinson]

So the implementation will be on m3.material.io and on GitHub or just on GitHub? Sorry this sounds confusing if I need to clarify let me know.

[asyncliz]

I don't know what the material.io team's plans are, but historically they've pulled our README documentation directly into the site, so it'll probably be in both

[hello-smile6]

I don't know what the material.io team's plans are, but historically they've pulled our README documentation directly into the site, so it'll probably be in both

Would it by chance be possible to download archives containing everything on the material.io and m3.material.io sites?

[reeceatkinson]

@asyncLiz any update on how to use it yet?

[hello-smile6]

@reeceatkinson The package isn't public yet. https://registry.npmjs.org/@material/web

[asyncliz]

Not yet! I plan on working on it next week. It might spill over into the next sprint, got a lot of stuff to do for M3 :)

[reeceatkinson]

@asyncLiz any update on the progress yet?

[hello-smile6]

next week

Nearly two weeks... 😦

[asyncliz]

next week

Nearly two weeks... 😦

Welcome to the life of a Google engineer 🙃

So small update: I'm stuck behind a bunch of infra setup for the new project. I'm working on it, but y'all might not see anything for a hot minute.