I'm a Solo Developer in Sweden. I Built an AI Chrome Extension to Cut Through Media Bias.

NoiseFilter — Thu, 18 Jun 2026 11:40:42 +0000

The world is full of noise. I built NoiseFilter to cut through it.

News is everywhere, and it's never been harder to know what to trust. Who benefits from this article? Is it pushing an agenda? Where did the story even come from? I built NoiseFilter because people deserve better than headlines designed to manipulate — no rumours stacked on top of rumours, no clickbait dressed up as journalism. Not to think for you, but to give you the tools to think for yourself.

What it actually does

NoiseFilter is a Chrome extension (Manifest V3) that analyzes whatever you're reading with one click. Not just news — it works on research papers, blog posts, and product pages too.

For each piece of content, it breaks down:

Article type — news, opinion, clickbait, PR, research, and more
Logical gaps — unsourced claims, missing evidence
The bias — whose agenda the framing serves
What's missing — important context left out
Independent comparison — how it stacks up against sources like Reuters, AP, and BBC

Think of it like a GPS. It gets you where you're going most of the time, but you might still miss a turn. NoiseFilter isn't perfect. It just gives you a clearer picture of what you're actually reading.

The stack

Nothing exotic, mostly chosen for speed of shipping as a solo dev:

Frontend: vanilla JS, Chrome's side panel API, Manifest V3
Backend: Vercel serverless functions (keeps the AI API key off the client)
AI: Claude Haiku for the actual analysis
Payments: Lemon Squeezy for subscription handling and license keys
i18n: Chrome's built-in chrome.i18n system, 15 languages from day one

I went with a strict freemium model: 10 free analyses, then a small monthly subscription. No accounts, no tracking, zero data retention by design — partly for GDPR simplicity, partly because it just felt like the right way to build a tool about trust.

What I learned shipping this alone

A few things that weren't obvious going in:

Chrome Web Store review is its own skill. My first submission got rejected over a missing host_permissions entry. Small things matter a lot at review time.
Marketing material takes longer than the feature itself. Screenshots, store descriptions, SEO-optimized copy — easily as much work as the actual analysis logic.
New accounts get throttled everywhere. Reddit's spam filter and AlternativeTo's submission system both gate brand-new accounts. If you're launching solo, budget time for that.
Saying no to features is a feature. I kept every new idea against one filter: does this need a database, time-based monitoring, or historical tracking that a free AI chatbot couldn't already do? If not, it didn't make the cut — at least not yet.

Where it's at

NoiseFilter is live on the Chrome Web Store right now, in 15 languages, with a free tier to try it before paying anything. I'm still early — figuring out distribution, collecting the first real feedback, deciding what to build next (a local analysis history is probably next on the list).

If you read a lot online and want a second opinion on what you're looking at, I'd genuinely appreciate you trying it and telling me what's wrong with it. That feedback is worth more to me right now than installs.

Found a bug or have thoughts? I read every message: noisefilter.feedback@gmail.com

🔗 Search "NoiseFilter" on the Chrome Web Store, or find it at getnoisefilter.vercel.app

DEV Community: NoiseFilter

I'm a Solo Developer in Sweden. I Built an AI Chrome Extension to Cut Through Media Bias.

What it actually does

The stack

What I learned shipping this alone

Where it's at