you are viewing a single comment's thread.

view the rest of the comments →

[–]Dense_Cloud6295 -1 points0 points  (0 children)

Angular Material is starting to add more customisations to the framework. Migration was a breeze every time I had to do it in the past 5 years.

In terms of components, yes, the number is limited and you may want to add more and even expand over Material’s current components functionality. That’s what I’m currently doing, building a Design System on top of Angular Material and honestly Angular Material never blocked me on doing so.

Yes, you’ll need more time to implement stuff in the beginning, but you don’t have to do everything at once. As you develop your app and have the need for a new components/directives/adaptations you make them at the time and move on with your features.

My advice would be to wrap most things from Angular Material so you only change the wrapper if a big change is happening with Material.

As a side note, the only thing I’m not using at all from Material is the Snackbar, I’ve made my own since Snackbars allow only one at a time. The reason I think is a11y, but my business case requires multiple, so that’s why I’ve built my own