components
components copied to clipboard
feat(Material): Material You Support
Feature Description
"Material You" was announced a couple of days ago: https://material.io/blog/announcing-material-you which looks to be a visual redesign of the Material design system. It appears to be arriving this Fall
It looks like it's going to become a little less opinionated in various aspects and that'd be great for those currently using Material today as a UI Library and having to hack the hell out of it to make it deviate slightly.
Quote from the description:
We’re introducing a new visual redesign that gives you the power to customize the look and feel of your phone across the whole system. With smoother animations, more intuitive notifications, quick settings and new widgets for your favorite people, Android will feel more personal and alive than ever before.
My guess is that this'll arrive upstream via MDC which is already being implemented. Will this be considered?
We should get this automatically once we've finished the transition to MDC components.
Will this be "opt in" in any way? Not that I dislike it, but for my web app it's perhaps not as fitting and I'd rather not stay on an old version just to keep the design
Any progress on this issue or is there any roadmap for this upgrade ?
Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.
Find more details about Angular's feature request process in our documentation.
Any updates here?
from issue: When is Material Web 3 Coming?
I am really confused about that. can someone give a clear answer here?
- Angular Material mdc is depend on material-components-web?
- Material Team is not focused on material-components-web anymore, they turn to material-web?
- Will Angular Material turn to material-web also or not going to have a Material You?
We're working directly with the Material Design group inside Google towards supporting design updates. No ETA just at this moment, but it's definitely something we're working towards.
MDC components were already outdated while Angular team were working on integration. Let's start to integrate new MWC (material-web) components :)
Glad to see I'm not the only one who's confused. I've been watching and waiting for a design update, literally for years - mainly for the density feature, but M3 is surely a welcome addition.
From what I've read:
- The Angular material team has been working on integrating with the MDC components for over three years and still actively working on it, known as the experiment components. They were planning to stablize and release them in version 14 but since v14 is imminent I doubt it's still on track;
- MDC is based on Material Design 2 (M2) and is not gonna be updated for Material You (M3) (https://github.com/material-components/material-web/issues/3050#issuecomment-1011464627)
- A new set of web components, known as the MWC, is based on M3, which will launch later this year;
- It doesn't seem Angular material has started to integrate with MWC yet, or it's still in a very early stage
- as @crisbeto stated, we'll get M3 when the transition to MDC is complete, seemingly contradicts with the facts above
Based on all these, can I assume we are not getting M3 in the near future?
Angular Material MDC migration has been a running gag in my company for years. Some kind of "When are you planning to release this feature ? -- Oh you know, when Angular Material will use MDC". It's a gentle joke but actually it's a sad situation because I feel (and I guess not to be the only one) like Angular Material will never propose real new features anymore (like two-direction drag-n-drop, more theming customization, more card capabilities or even time picker) and every real improvment are only reserved for Android and, more generally, for mobile devs. I'm aware that it's an open source project and the team has limited resource (just like every company) but it's hard to not feel impatience and frustration. That said, I will keep supporting and using Angular/Material because I love it. But guys please, do not let us down.
Is there any new information on the confusion in this thread? There doesn't seem to be any indication that Angular Material will support Material You (Material Design 3) from the fact that it references the old MDC implementation. We are looking into building a design on top of Material Design 3 and Angular Material, so I was wondering if this would be possible in the near future or if we should scrap that idea for the next year or 2?
The Material components offered now with Angular is the legacy components, which was released before Material 2 specification was out.
According to unofficial rumours the Material 2 components might be made available with Angular 15 release latter this year, but still it is not confirmed.
Having Material 3 components with Angular may not be a reality for the next several years. It might not happen at all.
According to unofficial rumours the Material 2 components might be made available with Angular 15 release latter this year, but still it is not confirmed.
Looking at v15 "next" release notes would suggest it's very likely they'll be rolled out with the release. Now, that's not to say it won't go through a "Developer Preview" period like some of the big new features that've been released recently, but even in that case, it seems very close to seeing the light of day: https://github.com/angular/components/releases/tag/15.0.0-next.0
v15 will promote the MDC-based components ot stable. These components are a stepping stone to future iterations of the design system (M3). If you peek on ongoing PRs, you'll see the theming mixins for many of the components transitioning to design tokens, which is the basis for M3.
I noticed that! I'm excited to see a greater use of CSS Custom props. Do you foresee that impacting how teams configure the overall theme using the Sass theming API?
Yeah, any support for M3 will be part of a larger update to Angular Material's theming system. While the design isn't fully complete, it will likely involve a lot more customization options.
@jelbourn is there any way that one could contribute to moving forward with this change?
Unfortunately no, we're still waiting on deliverables from the Material Design folks to be able to move forward on the Angular side.
@jelbourn Thanks, Are there already specific issue(s) on the Material Design side that we can point to here? Maybe the community wants to support them to speed things up here :)
I don't think so, since the changes relate to the underlying Material Design token definitions for web which I don't think have been formally published anywhere.
Any updates?
Some incremental work transitioning to design tokens is associated with the Angular 16 release.
I also spotted the barest of hopeful hints from @mgechev of the Angular team on the general Material You development arc (along with further context that may be of interest).
Additionally, in the broader context of Angular 16, a brief Angular 16 release summary I found insightful also notes this Material You development.
Are we getting Material 3 styles in Angular Material?
Any updates?
Is there any update on Angular Material 3 support?
Any update about Material 3 ?
In a recent tweet @SerkanSipahi mentioned a PR for the initial implementation of Material 3 theme objects that has since been merged as part of a current Angular Material benchmark in the Angular Roadmap towards enabling Material 3 capabilities. As another marker of progress also note that legacy Angular Material components (pre-MDC) will be dropped in Angular 17.
MWC is 1.0 and ready to use in production!
https://twitter.com/materialdesign/status/1714378297696461160?t=hDBDncKLA-qWuXPBBL6PCA&s=19
Can someone please explain the relation between Angular Material and Material Web? Is Angular Material going to transition from Material Components Web -> Material Web next or will those be kept completely separate? What's the plan here?
cc @ciriousjoker
Material Web uses the Lit Framework as the core engine and Angular Material uses the Angular Framework as the core engine.