// the take
A two-layer Blazor UI kit: headless accessible primitives plus pre-styled shadcn/ui-flavored components, covering everything from buttons to a DataGrid, Scheduler, Gantt chart and ECharts-based charting. Aimed at .NET teams who want a shadcn-equivalent for Blazor without hand-rolling Tailwind/ARIA/keyboard plumbing themselves.
The QR code and barcode components are hand-written SVG encoders (not wrappers around a JS lib) and were checked symbol-for-symbol against zint and zxing-cpp — that's the kind of correctness claim you can actually verify. RTL support goes past CSS flipping: logical properties are enforced by a convention test, and gesture-based components explicitly read direction at interaction time rather than baking in a static flip. Accessibility and keyboard handling are implemented in the headless primitives layer, not retrofitted onto the styled components, so you get it 'for free' using either layer. Playwright regression coverage runs across Server, WASM and Auto in two browser engines, which is more end-to-end testing rigor than most component libraries this size bother with.
v4 requires .NET 10 minimum and drops 8/9 outright, so anyone not already on .NET 10 is blocked or stuck on the older major — and the fact that there's already a V3 and V4 migration guide for a 673-star project suggests the API is still moving under you. Every component needs an interactive render mode (Server/WASM/Auto); plain SSR pages get nothing, and the README's own lengthy workaround for per-page interactivity breaking layout chrome in MainLayout is a sign this is a real footgun people hit, not a documented edge case. The surface area is enormous — 52+ styled components, 35 primitives, plus a DataGrid, Scheduler, Gantt and Pivot grid — for what still reads as a small or single-maintainer project, which is a lot to keep consistent and bug-fixed long term. The 'Enterprise Components' naming for DataGrid/Scheduler/Gantt/Pivot sits oddly next to the Apache 2.0 license with no explicit statement they'll stay free in future majors — worth confirming licensing intent before building on those specific components for anything long-lived.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →