Closing Angular's aesthetic gap

Closing Angular's aesthetic gap: building AxisUI, a signals-first component library

If you've built an Angular product in the last two years, you've felt this. The libraries that redefined what "modern component design" looks like — shadcn/ui, Radix, Park UI — showed up for React and mostly stayed there. Angular got thin ports, abandoned ports, or nothing.

So Angular teams keep making the same trade: adopt Angular Material and accept its Material-Design aesthetic everywhere, or wire up Tailwind plus a headless-primitive library by hand and absorb the cost of keeping fifty components visually consistent yourselves.

I got tired of that trade, so I built the third option.

AxisUI is a UI component library for Angular 20: 100+ components, signals-first, standalone by default, styled with Tailwind v4 and OKLCH tokens, accessible to WCAG 2.2 AA — with the accessibility checks running in CI, not just claimed in a README. Every component is MIT.

• 
  Live demo:
  


• 
  Storybook:
  
  
  

  
  
  
  Where it's at, honestly
  

  
  
  

  It's new, and it's mostly one person's work. The API surface is stable enough that I've built those eight templates on it without fighting it, but it hasn't been battle-tested across hundreds of teams yet. That's exactly why I'm posting: I want Angular developers to try it, break it, and tell me where it falls short.

  
  
  

  If it saves you from the Material-or-hand-roll trade even once, it did its job.

  
  
  
  
  
  • Try the demo →
    
  
  
  • ng add @axisui-ng/angular
  
  
  
  
  

  What would make you switch a real project to it? I'm reading every reply.

  Vollständiger Original-Bericht

  Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.

  ↗ Original-Artikel auf dev.to lesen