Last month I shipped Nugetz.dev.
It’s a modern interface for searching the NuGet registry.
This isn’t a startup launch.
It’s not a product pivot.
It’s not a monetization play.
It’s just something that bothered me for a while.
And it was heavily inspired by what the community did with npmx. A cleaner, faster way to explore npm.
That project made me think: why don’t we have something like this for NuGet?
So I built it.
The Frustration
NuGet is massive. It powers a huge part of the .NET ecosystem.
But the search experience hasn’t really kept up.
When I’m evaluating packages, I want to move fast. I want to quickly scan:
- Is this maintained?
- How often is it updated?
- How widely is it used?
- Does it look abandoned?
Instead, I often feel like I’m fighting the interface.
Search should feel instant.
Scanning results should feel effortless.
Comparing packages should feel natural.
So I built the version I wished existed.
What Nugetz Is (and Isn’t)
Nugetz is intentionally simple:
- Fast search
- Clean layout
- Minimal UI noise
- Focus on readability
No login.
No ads.
No growth hacks.
Just a better way to explore packages.
It’s not trying to replace NuGet.
It’s not trying to compete with Microsoft.
It’s just a sharper interface on top of the registry.
Why Bother?
Because developer tooling matters.
We spend hours every week inside search pages, documentation, package registries, dashboards.
Small UX improvements compound.
If something saves you even a few seconds each time you search, over months and years, that adds up.
Good developer experience is leverage.
What I’d Love
If you use .NET, try it.
Break it.
Tell me what’s missing.
Tell me what feels better.
Tell me what doesn’t.
The .NET ecosystem deserves good tooling.
Even small improvements matter.
That’s it.
Top comments (0)