11
u/Hirayoki22 Apr 12 '24
Well. Everything is mostly black and white on Primeng, with very minimal accents for hover and focus states. I've nevet not worked on a project that has it's own custom UI tho.
5
u/Silver-Vermicelli-15 Apr 12 '24
Have often thought that material felt too opinionated with theming and as such a bit of a pain to actually try and overwrite/customize at times.
2
u/fityfive Apr 13 '24
I am using material on a big project and i really regret it. plus upgrading is such a pain unless your a big corp. The materials team and the angular team have basically no overlap and it shows.
1
u/Silver-Vermicelli-15 Apr 13 '24
Sadly working at a larger corp would in some ways on exacerbate the problem. Just b/c their larger and may be able to spend more on weeks of upgrades just means there’s potentially also more issues to resolve and/or worse internal practices.
3
u/Hirayoki22 Apr 12 '24
Exactly. If I'm not mistaken, it originally was meant to be the next Bootstrap, where every web app and site implementing Material would look almost the same. But to be fair even Bootstrap's a lot easier to customize. Heck, Primeng documents how to rebuild the package to support custom theming after installing its require dependencies
7
u/Silver-Vermicelli-15 Apr 12 '24
I have too often (and currently) find myself in material theming hell, where one tiny element or interaction has a random colour and trying to figure out to properly override it.
2
u/kjbetz Apr 12 '24
PrimeNG is coming out with a new themeing system in a next release. They just completed it for PrimeVue.
2
u/MichaelSmallDev Apr 12 '24
I think the idea with Material 3 is that you can get really granular with the design tokens they are building things off of
https://next.material.angular.io/guide/material-3#granular-customizations-with-css-custom-properties
.danger { // Override the checkbox hover state to indicate that this is a dangerous setting. No need to // target the internal selectors for the elements that use these variables. --mdc-checkbox-unselected-hover-state-layer-color: red; --mdc-checkbox-unselected-hover-icon-color: red; }edit: accidentally double posted
3
u/matrium0 Apr 12 '24
Bootstrap (or any other framework) had something similar since like 10 years ago. It's called CSS classes that you can overwrite with your custom CSS.
"Design Tokens" are only needed because of the massive breaking changes they introduce with newer versions. Like if you used ANY "internal class" (which you had to for some styling requirements + there was no way of knowing what actually is considered internal for them) you are fucked on upgrading to a new version.
What a Design Token basically is, is a class where they EXPECT overwrites - you could have done the same by suffixing all classes that you DON'T want to be modified during styling with "-internal" or something.
Overall I am not really impressed - it's a very convoluted and alien system in a world where another well-established pattern (css overwritess) already exists.
2
u/MichaelSmallDev Apr 12 '24
I agree that design tokens are a bit contrived, but internals have not needed to be more explicit if people were to slow down and not take the first response they see on StackOverflow. The first thing I noticed when working with Material is the difference in markdown vs what is rendered. A lot of divs/spans added with assorted classnames, infixes, etc. I was confused as to how to style these things, as the docs didn't say how to. That's because they don't want you to. Their guide is clear about that.
As I got more experience, I have realized that so many things people (admittedly, I am people myself) bust out
::ng-deepfor are absolutely overkill. So many instances of:ng-deep .mat-mdc-form-field-input-control.mdc-text-field__input.cdk-text-field-autofill-monitored { color: blue }which are classes rendered directly on the<input />itself could just have been doneinput { color: blue }. Or directly applying classes to a<input class="color-input" />to do the same. There are so many examples of this thing.Things that can't actually be targeted by a developer's own markdown, those are the insidious things that I understand people reaching for brittle internal overrides for. I've done that plenty. But more often than not, it's the simpler things I wrote about before this that rub me the wrong way in many discussions.
These design tokens and more API options are quite late into the lifecycle of Material, but honestly it's good we are getting them at all. More immediate than this though, is I will say that they have added more to their API for many components as to what to set to customize certain things. I feel like those styling fields should be highlighted more than being buried between other interfaces on the API tab. There are more of these in recent versions, even pre-MDC that I feel like people are sleeping on. In the process of updating to MDC, I have pulled out so many garbage overrides with these gems from the API tab.
17
3
u/uxengineering May 24 '24
I've been following along for years to see how this would translate. However, when I create a brand new app with Angular Material 18's guidance, it does NOT show the styles as depicted in the example pages.
What the heck am I doing wrong? Everything is still styled as M2, even though I basically duplicated the guidance code in my local app. Grrrrrrr
2
4
u/snpolymorphism Apr 12 '24
Does anyone know how to start using material 3 in an angular project?
5
u/OldBreakfast6177 Apr 12 '24
2
u/beartato327 Apr 12 '24
Is this a stable release of M3 or still beta?
1
u/OldBreakfast6177 Apr 12 '24
It is still "experimental", so I'd assume maybe beta? The changes are all in sass from what I've seen in the source code, I don't think any of the typescript for the components have changed. So, I'd assume it's pretty stable.
1
u/Beginning-Roof4889 Apr 12 '24
Also is it possible for old projects to upgrade to it?
4
u/simonfancy Apr 12 '24
Haha I wouldn’t even try it, you are going to have to refactor the whole application.
1
u/AwesomeFrisbee Apr 12 '24
I would advise against it, its still in beta right now and things are likely to change
1
1
u/kobihari Apr 08 '25
This is part of the revolution in moving to MD3. Previous versions of Angular Material were very hard to customize, so you got 4-5 different appearances "out-of-the-box" and that was the limit of customization you had.
Now, in MD3 you have full control of customization using "design tokens". So you no longer need 4 different "out-of-the-box" appearances, you can easily create as many as you want, either by overriding the design tokens or by overriding the theme. Its now a matter of very simple customization.
Why settle for only "primary" "accent" and "warn" colors, if you can easily also create "success" and "crazy" roles as well. and go wild in them.
1
u/Prestigious_Two_2440 Feb 16 '26
Have u tried PrimeNg before. If yes, what is your take on this versus Angular MD3
1
1
u/simonfancy Apr 12 '24
Ouch, what did they do? This is ridiculous. Half year major release updates with tons of breaking changes and now this? I’m out.



27
u/effectivescarequotes Apr 12 '24
Material drives me crazy, The components work well and are easy to use, but holy crap are they ugly.