I run outreach for a small personalized-gift store — photo blankets, custom mugs, ornaments, that sort of thing. The store has 1,920 products. Shoppers kept telling us the same thing: they knew who the gift was for, but they froze when they had to pick from hundreds of options. So I built a tiny browser extension that asks three questions and narrows it down to three gifts. The whole thing runs on zero permissions.
Why zero permissions
Most gift-finder extensions ask for broad access — read your browsing data, track the sites you visit. That is a trust killer for a shopping tool, and it is also unnecessary here. The extension I built, Epic Gift Finder, has no permissions key in its manifest at all. It asks the browser for nothing at all — no access to your tabs, no background process phoning home, no analytics of any kind. At the end of the day it is just a small popup window, plain HTML and CSS with a handful of JavaScript behind it. Click a suggestion and the store's category page opens in a normal tab, same as if you had typed the address yourself. Manifest V3 makes this easy. The manifest declares the popup, the icons, and nothing else. If a future version ever needs storage or network access, that will be a deliberate decision with a reason users can see — not something slipped in from day one.
How the quiz works
Three questions, no typing required:
- Who is it for — her, him, kids, or a pet lover.
- The occasion — a birthday, Christmas, an anniversary, or nothing in particular, just because.
- What is the budget — under $25, $25 to $50, or over $50.
Behind that is a small scoring table in plain JavaScript. Each answer points at a few product categories, and the budget answer filters out anything that starts above the range. The extension scores the matches, picks the top three, and renders them as cards with a short line each about why that gift fits. Every link in the table points at a real category page on Epic Personalized Gifts — thirteen of them, each one clicked and checked by hand before I shipped anything. A dead link inside an extension is worse than no extension at all, because the user has already trusted you once by clicking.
What the build actually looks like
Four files make up the whole thing. There is the manifest, the popup page, its stylesheet, and one JavaScript file with roughly two hundred lines in it. No framework. No build step to run before it works. When you answer the three questions, the code matches your picks against a small table and shows the best three. It never calls out to a server or a model — the whole thing runs right there in the popup, so the answer shows up the instant you click. You only need a connection when you open one of the store links. Testing was manual and boring in the best way. I loaded it unpacked in Chrome, ran every combination of answers, and checked that the three suggestions always made sense for the inputs — no mug for a pet lover when a pet pillow exists, no $140 blanket in the under-$25 bucket. Then I made the two 1280×800 store screenshots the Chrome Web Store listing asks for.
What I would do differently
I would have verified the links earlier. My first version had two category links copied out of an old spreadsheet, and those slugs had changed on the live site since. The quiz itself ran fine — but two of its suggestions would have opened dead pages. No automated test I know of would have caught that. These days the rule is simple: before any release, I open every single outbound link myself and watch it load. The extension is live on the Chrome Web Store now — Epic Gift Finder. It's free, no sign-up, no tracking. The shop behind it is Epic Personalized Gifts, and the same package ports directly to Edge and Firefox. If it helps even a few shoppers stop scrolling and actually pick a gift, the weekend was worth it.
Top comments (0)