How the opportunity score is built
Learn how Extensions Archive turns public Chrome extension signals into a sortable rebuild opportunity shortlist.
1. Collect public signals
The database combines visible Chrome Web Store signals with GitHub discovery where source code is available. The goal is fast research, not a replacement for your own due diligence.
2. Score demand and rebuild friction
Each row is scored from users, review volume, rating quality, Manifest version, source availability, update age, and estimated implementation complexity. Items last updated before 2022 receive an extra reduction because very old products often need more recovery work.
3. Review the shortlist
Use the Browse table to sort, filter, and inspect candidates. Strong rows should still be checked manually for trademark risk, current availability, code quality, and whether users still have the same problem.
Browse opportunitiesBuild it
Every opportunity comes with a ready-to-use AI build prompt and a clear Chrome Web Store submission path, so you can go from shortlist to shipped extension.
You are a senior Chrome extension engineer and product-minded technical founder. Act as the implementer: decide, don't ask. ## Opportunity brief Name: Print Friendly & PDF What the original does: reflows a page into a clean, ad-free print/PDF layout with font, margin and image controls. Signals: 800K users, 4.4 from 3K reviews, MV2, complexity 2/5 Reference links (read these first): - Reference repository: https://github.com/example/print-friendly - Chrome Web Store listing: https://chromewebstore.google.com/… ## Step 1 — Feature reverse-engineering MUST for v1 vs LATER, plus the one core workflow… ## Step 2 — Technical plan MV3 surfaces, storage keys and types, event flow, folder tree… ## Step 3 — Execution order Numbered build steps, each verifiable in the browser… ## Step 4 — Code manifest.json, service worker, popup, content script — complete files…
- 1.Create a Chrome Web Store developer account and complete the publisher registration.
- 2.Build the extension locally with a Manifest V3 manifest.json, source files, and icons.
- 3.Load unpacked from chrome://extensions with Developer mode on.
- 4.Test permissions, service worker behavior, storage, and content scripts.
- 5.Prepare listing assets: name, description, screenshots, icon, and privacy policy.
- 6.Zip the extension folder contents with manifest.json at the root.
- 7.Upload in the developer dashboard, complete the listing, and submit for review.