Building Blazor Blueprint alongside a real product gave Mathew Taylor a practical way to test his components; releasing them publicly brought early validation, outside feedback, and a fork that initially felt uncomfortable. Nine months later, he sees all of it—including that first reaction—as part of learning to maintain an open-source project.
Why I started building Blazor Blueprint
In a September 22, 2026 retrospective, project creator Mathew Taylor explains that his company decided in December 2025 to build a commercial product, and he chose the technology. He wanted one technology across the stack and took a serious look at Blazor. He liked building with C# end to end, but the visual style of the UI libraries he considered did not fit the product he had in mind.
As an Amazon Associate I earn from qualifying purchases.
Taylor wanted what he describes as “the modern, clean look of shadcn/ui in Blazor.” Rather than return to a JavaScript frontend, he started making components himself. The project’s official repository describes Blazor Blueprint as inspired by shadcn/ui and Radix UI; that is a design lineage, not a claim that the projects have equivalent scope or implementation.
Free tools Windows power users keep installed
One-click scans. No signup required.
Building for a real product shaped the library
Looking back, Taylor calls building components while building a real product his best decision. The components went into use immediately, so the product gave him feedback on what worked and what did not. That experience made the library more than an exercise in assembling a public component catalogue: he was using it in the setting it was meant to serve.
#1 Best Overall
That is a useful lesson from his account, not proof that every library should begin inside a commercial product. The more specific point is that real use gave Taylor a concrete way to notice friction and refine his work before asking whether other Blazor developers wanted it too.
The first response was validating—and the first fork felt strange
Taylor remembers seeing the first GitHub star, then notes with a little self-deprecation that he had given it to the project himself. After he posted about it on Reddit, he says Blazor Blueprint passed 160 stars in its first week. For a first open-source release, he describes that response as meaningful validation. The milestone is Taylor’s account, not an independent measure of users or adoption.
Rank #2
The less comfortable surprise was seeing someone fork the repository and build in a different direction. Taylor says it felt strange, particularly because this was his first experience putting code into the open-source community. With nine months of hindsight, he sees that moment as part of learning how participation works: once code is public, other people can take it somewhere the original maintainer did not choose. His initial discomfort and his later acceptance can both be true.
Where Taylor says the components are used
Taylor reports that Blazor Blueprint is used in his company’s commercial product, in several client projects, and in internal tools. He names Beaacon, which he describes as an anonymous website analytics tool, and Merlin, which he describes as a tool for managing ISO 27001 requirements, as examples he can share. These are author-reported uses and product descriptions, not independently audited deployments or customer references.
Rank #3
What changed in nine months
Taylor says the project grew from more than 160 stars in its first week to over 600 by the time of his retrospective. The official repository’s README snapshot around the same period listed 639 stars and 53 forks. The counts describe different points and sources; they are volatile GitHub counters, not user numbers, download totals, or evidence of quality.
In the retrospective, Taylor describes version 4 as adding many components and moving the library closer to major Blazor libraries in coverage. He says version 4.1 adds a Scheduler, Pivot Data Grid, Rose, Sankey and Map charts, Signature Pad, and Barcode and QR Code components, along with speed and stability improvements. He described a Spreadsheet component as coming soon at the time of that post; that was a statement of the then-current plan, not a present roadmap commitment.
Rank #4
What the current README says about trying it
The repository README documents a two-layer design: pre-styled components and headless primitives. That gives a prospective user a practical choice between starting with styled UI and using lower-level building blocks. The README also describes ARIA attributes and keyboard support, dark mode, and theme compatibility; these are project claims, not the results of independent accessibility testing.
- Framework: The README says version 4 requires .NET 10 or later and an interactive Blazor render mode.
- Packages: It lists the NuGet packages
BlazorBlueprint.ComponentsandBlazorBlueprint.Primitives. - License: It lists Apache License 2.0 for Components and Primitives.
Framework requirements, package instructions, license details, and repository counters can change. Check the README and release information for the version you plan to use before adopting it.
The lesson I take from Taylor’s account
Blazor Blueprint began with a specific design frustration, grew through use in a product Taylor was already building, and became more than a private solution after other developers responded. The fork mattered for a different reason: open source also means giving up some control over where public code goes. Taylor’s nine-month perspective does not turn those experiences into a formula for success, but it does show how a first-time maintainer can learn from both encouragement and unease.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
