I wanted shadcn/ui for Blazor. It didn’t exist. So I built it.

If you've spent any time in the React ecosystem over the past two years, you've seen shadcn/ui everywhere. And for good reason — it solved something fundamental that every other component library got wrong. I'm a Blazor developer. And for the longest time, watching shadcn/ui take over the React world felt like watching a party happening through a window. This is the story of why I built NeoUI, what I learned, and how Blazor developers can now have the same thing. The shadcn/ui moment When shadcn/ui launched, it didn't just ship a set of components. It shipped a philosophy. The insight was simple but radical: you shouldn't be fighting your component library . Most UI libraries are configuration-first — you install them, accept their design system, and spend half your time overriding their opinions. Customising a MUI component to not look like MUI is a rite of passage every React developer has suffered through. shadcn/ui flipped this. Instead of locking you into a package you can't modif