DEV Community

Cover image for I built a Web3 tools directory because everything is scattered
Graham McCann
Graham McCann

Posted on

I built a Web3 tools directory because everything is scattered

I built a Web3 tools directory because everything is scattered

Creating anything in Web3 is weirdly harder than it should be.

Not because of the tech itself, but because everything you need is scattered everywhere.

You find one tool on Twitter, another buried in a GitHub repo, then a random blog post from 2021 that might still be relevant… or might not.

It slows everything down.


The problem

If you're building in Web3, you've probably experienced this:

  • You need a tool for something specific
  • You search Google and get outdated results
  • You check Twitter and find threads with half-broken links
  • You dig through GitHub repos with little context

There’s no single place that feels reliable or complete.

Everything is fragmented.

And when you're trying to build something quickly, that fragmentation becomes friction.


Why this matters

In most industries, tools are easy to find.

You’ve got directories, marketplaces, comparison sites.

In Web3, it’s still messy.

That means:

  • More time searching
  • Less time building
  • More duplication of effort
  • Missed tools that could actually help

It shouldn’t be like that.


What I built

So I built Web3ToolLaunch.

👉 https://www.web3toollaunch.com/

It’s a simple directory focused on one thing:

Making Web3 tools easier to discover.


What you can do with it

Right now you can:

  • Browse tools by category
  • Explore areas like DeFi, AI crypto, NFT and infrastructure
  • Discover tools you probably wouldn’t have found otherwise
  • Submit your own tool

No accounts required, no friction.

Just a clean list of tools that are actually useful.


How it’s different

I’m not trying to build another bloated marketplace.

The focus is:

  • Simplicity
  • Discoverability
  • Clean structure
  • Useful categories

Over time, the goal is to make this a go-to place when you're starting a new Web3 project.


Early challenges

A few things became obvious straight away:

1. Seeding content

A directory is only useful if it has content.

So the early phase is manually adding tools and making sure the categories make sense.

2. Quality vs quantity

It’s tempting to add everything.

But a directory full of low-quality tools is worse than a smaller, curated one.

3. Getting submissions

The real growth comes when other founders start submitting their tools.

That’s the next big step.


What’s next

I’m planning to:

  • Expand categories (more specific niches)
  • Add better filtering and sorting
  • Highlight featured tools
  • Improve SEO pages for each category

Long term, I want this to become a proper resource for developers and founders building in Web3.


And Finally ...

Web3 has no shortage of tools.

What it lacks is organisation.

That’s what I’m trying to fix.

If it saves someone a bit of time, it’s already worth it.

Top comments (0)