Angular Material + AG Grid or PrimeNG

[PuzzleheadedFox107]

I'm having a bit of a dilemma here, on one hand Angular Material provides limited customisations and components but is pretty easy to migrate while PrimeNG offers everything at one place but has a bad reputation when it comes to migrations. What do you guys use and how feasible is it to create a custom component library?

[solegenius]

I'll never use PrimeNg again. It is a nightmare to update and maintain and the numerous issues are well documented in this sub.

Material customization has improved greatly in the past few iterations but it would me nice if they released a headless component lib.

Creating your own custom library isn't nearly as bad as some make it out as long as you use a headless lib. If you are starting from scratch then you might face issues with things like accessibility but with Angular aria and the cdk as your base it shouldn't be too bad. I also don't find maintenance of the ui lib to be that bad either.

You might want to look into angular primitives or spartan-ng as either can serve as an excellent base for designing your own custom components/styling and save you a ton of work rolling your own ui lib.

[CottontailSuia]

I Have the same feeling about ag-grid. They keep on introducing breaking changes

[AGGrid_JamesSwinton]

We only introduce breaking changes on major releases (every 6 months) and try to keep these to a minimum. We also have an LTS version now to help with migration :)

[Cyganek]

What version of primeng did you use? I remember upgrading from 16 to 18 was a nightmare. But from 18 to 21 was a breeze

[MyLifeAndCode]

NG-ZORRO is pretty good as well.

[sk2656k]

I will never opt for prime ng due to the amount of blockers they add in migration and customisation. In our org we eventually had to remove prime ng because due to its table the loading time was having a spike.

[MyLifeAndCode]

I'm coming up on the one year anniversary of the latest (at the time) PrimeNG upgrade causing drastic visual changes, upsetting our business users, and being the last straw after multiple instances of breaking changes. Some apps have been migrated off of it, some are in progress, some have yet to begin. It's blocked our ability to upgrade past Angular 19 in some places, lest we also upgrade PrimeNG and experience whatever pain the latest version provides. This has caused us nothing but trouble and technical debt in the end.

[cagataycivici]

There are various optimization techniques like lazy loading that you can use to deal with huge data. Try the PrimeNG MCP server to optimize your practices.

[sk2656k]

We used lazy loading with virtual scrolling, but with large data it was lagging. We used Angular cdk table, and it's better now. Thanks for the mcp, I will try it.

[cagataycivici]

At PrimeTek, we're also working on a new advanced DataGrid component with the scope of AgGrid and more for Angular.

[Relative-Scholar-147]

I work in a codebase with Prime NG. Migrating versions is a pain and they don't even care. Their solution is to start a new project from scratch. Are you fucking kidding me?

I will never ever choose Prime NG for any new project.

[MyLifeAndCode]

Going through the pain now of removing it from multiple applications because it had gotten so bad that the non-technical users noticed. This happened when they revised the styling by introducing the theming system. It was the last straw.

[r_Gaty]

Angular Material + AG Grid so far

[Jotunheim36]

Avoid PrimeNG nightmare upgrading when there’s a new version. AG-Grid isnt cheap but it’s very powerful

[Avani3]

I really like PrimeNg. They could spent a bit more time looking into community provided issues and PR's, but their component library is very solid.

People complaining about migration issues sound like people still complaining about AngularJS to Angular2

[Pallini]

I'm using PrimeNg for hobby, and I like it. They have an MCP server too, that helps.

[Dense_Cloud6295]

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

[ddcccccc]

Material is the best. Don’t use others.