MBy what you built

Get feedback on your Chrome extension from people who install it.

A Chrome extension gets about one chance: the install prompt with its permission warning, then a first click on an icon that may be hidden behind the puzzle piece. Makers on the wall install yours, use it on the sites they actually visit and tell you where it lost them.

Get your first testersSee what’s on the wall
  1. 1 · Post itPaste your link, say what testers should look at. It goes on the wall right away, free.
  2. 2 · Test oneClaim another maker's project and write down what broke. Each report earns 20 credits.
  3. 3 · Read yoursMakers test your project. Each report arrives locked with an excerpt; 20 credits unlock it in full.

Why extensions need their own kind of test

Extensions run on other people's websites, next to other extensions, in browsers set up in ways you never tried. Content scripts that work on your test page break on a real one. A Manifest V3 service worker that goes idle drops state you thought was safe.

And the permission warning is the first copy users read. "Read and change all your data on all websites" stops a lot of installs; testers will tell you whether your onboarding explains it.

Getting the extension to testers

  • Published or unlisted on the Chrome Web Store: the simplest, and it tests the real install flow.
  • A .zip to load unpacked: put the steps in the private brief (chrome://extensions, Developer mode, Load unpacked).
  • Say which Chromium browsers you support (Chrome, Edge, Brave, Arc) so testers report on the right ones.

Web projects open for testing right now

Real projects from the wall. Test one while you wait for your own reports.

See your listing before you sign up

Paste your link. We read the name, the icon and the cover, and show you the card other makers will see on the wall. You only create an account when you publish it.

Free. No card, no account yet.

Questions

Can testers try an extension that isn't published yet?
Yes. Share a .zip and the load-unpacked steps in the private brief, or publish it as unlisted on the Chrome Web Store and share the link. Unlisted tests the real install flow.
Do testers need to use Chrome?
Most Chromium browsers run Chrome extensions. Say in your brief which ones you support, and testers report on what they use.
What should I ask testers about permissions?
Whether they understood why each permission was needed, and whether they'd have installed it at all after reading the warning. That answer is worth more than any bug report.
Is Makers Wall really free?
Yes. There is nothing to pay and no card to add. You pay in tests instead: each report you write for another maker earns 20 credits, and 20 credits unlock a full report on your project.
Who tests my project?
Other makers with projects on the wall. They are good at spotting broken flows, confusing copy and bugs. They are probably not your target customers, so treat their reports as a sharp first pass before launch, not as market research.
What if a report is lazy?
You see an excerpt before you unlock it. Once it's unlocked you can accept and rate it, or request changes once with a message. Ratings follow testers around: a report that says "nice app!" earns a low one.

Put yours on the wall.

Free. Test another maker’s project, get honest reports on yours.

Get your first testers