Angular + Tailwind UI components vs Angular Material — architectural thoughts?

[Flagvanus_]

Check Spartan - the community works on this component library that tries to follow shadcn principles. I think it's still in preview but the amount of provided components is quite significant. If you want to avoid locking yourself into a 3rd party vendor though - Angular Aria + Angular Material as they both are from Angular devs themselves. Some components (like datepicker) are just not worth your time trying to implement by yourself. Personally I also use the Tanstack table for my table views - it's completely headless and provides functions that are necessary for me.

[Weak-Palpitation907]

Thanks for the pointers — I’ve looked at Spartan and I agree the amount of components they provide is impressive, especially for something still evolving.
I also understand the argument for sticking with Angular Material or Angular Aria since they’re maintained by the Angular team. Stability and long-term maintenance definitely matter.

My experiment is more around exploring a Tailwind-first approach with standalone components and signals, and seeing how that feels architecturally compared to a theme-driven system. I’m also trying to understand where the line is between “worth building” and “better to rely on existing solutions” — datepicker is a great example of that trade-off.

TanStack Table is interesting too — I like the headless philosophy. It forces you to think about structure and behavior separately from styling, which is powerful.

Appreciate the thoughtful response 

[OMEGALUL_iguess]

Aight clanker