2
3 Comments

I scraped 2,000 Chrome extensions to find abandoned ones that still have users. Here's the pattern.

I kept noticing the same thing while browsing the Chrome Web Store: extensions with 100k+ users, hundreds of reviews, and a developer who clearly walked away years ago. The reviews are full of "this used to work," "please update," "does anyone still maintain this?" — and nobody answers.
That gap is interesting. High install base + active complaints + absent owner isn't a dead market. It's a market that's still alive but no longer served. Different from an extension nobody installs anymore, which is just dead.
So I built a small pipeline to find them at scale. Roughly the steps:

  1. Pull a few thousand extensions and their public stats (installs, rating, last update).
  2. Filter for the "abandoned but loved" shape — decent install base, rating slipping, no update in a long while.
  3. Read the 1–2 star reviews and pull out what people are actually angry about — the specific missing feature or broken behavior, not just "it's bad."
    The thing I had to fix early: my first scoring rewarded "abandoned the longest." Wrong. An extension untouched for 8 years has lost its users — the complaints stopped because everyone left. The real opportunity is the one abandoned 12–24 months ago: long enough that the owner's clearly gone, recent enough that the users are still there and still annoyed.
    A few honest caveats I learned the hard way:
  • High users + recent complaints = opportunity. Low users + silence = just dead. Don't confuse them.
  • Some "abandoned" extensions are being quietly absorbed by the browser itself (tab features, etc). Forking those is building on melting ice.
  • "Hard to copy" is the wrong question. "Does rebuilding this actually bring someone money/users" is the right one.
    Curious if others here have rebuilt an abandoned tool and how it went — did the existing angry user base actually migrate, or did you have to win them from scratch?
    (I ended up packaging the full list of opportunities I found into a small report — happy to share where if anyone wants it, but mostly posting because the "alive vs dead market" distinction took me a while to see and I figured it'd be useful here.)
on June 18, 2026
  1. 1

    the 12-24 month sweet spot is the key insight. also worth adding: the angry 1-star reviews are your pre-built feature roadmap, in the users own words. thats validation data most founders would spend months trying to collect.

    one risk to watch though: extensions with permissions like "read browsing data" or "access all sites" carry inherited trust. users installed under the old developers name. if you fork and update, some portion will notice a new developer in their extensions page and uninstall. factor that attrition into your install base projections.

  2. 1

    The migration question is the trap. Those angry reviewers feel like a warm list, but the store gives you no way to message another extension's users, so the install base almost never moves over directly. What you actually inherit is the search demand: the dead extension still ranks for its keywords and people type its name looking for a replacement. I'd score opportunities on the keyword volume it still owns, since raw install count mostly measures users you can never reach.

  3. 1

    What I found interesting wasn't the abandoned extensions.

    It was the assumption that an angry user base automatically transfers with the replacement.

    Those users are clearly unhappy, but that doesn't always mean they're actively looking to switch.

    I'd be curious how often those two things end up being the same.

Trending on Indie Hackers
I got my first $159 in sales after realizing I was building in silence User Avatar 50 comments I spent more time setting up cold email than actually selling. Here is what fixed it. User Avatar 41 comments Three Days Before Launch, I Let My Own Tool Tear Me Apart User Avatar 31 comments I just wanted to taste AI coding tools. A week passed. User Avatar 28 comments I got tired of rewriting the same content for 9 different platforms. So I built Repostify. User Avatar 25 comments A pattern I keep seeing in EdTech: traffic isn't usually the problem. User Avatar 21 comments