I will build chrome extension,browser extension,manifest v3,scraper,web store listing


About this gig
Chrome extension development, Manifest V3, built to pass Web Store review on the first submission.
Google rejects most first submissions for four reasons and none of them are code quality. Permissions in the manifest the extension never calls. Host permissions set to all_urls when one domain would do. No privacy policy URL, which is required the moment you touch a token. And remotely hosted code, which trips Blue Argon, the violation nobody sees coming.
I build the whole thing: popup, options page, side panel, content scripts, a service worker keeping state in chrome.storage so it survives idle termination, chrome.alarms, chrome.identity and OAuth, declarativeNetRequest instead of blocking webRequest, REST and GraphQL integration, webhooks, and cross browser builds for Edge and Firefox.
Then the listing. Screenshots, privacy policy, and permission justification written the way reviewers want, so you sit in a 2 to 5 day queue instead of a rejection.
Scrapers, form fillers, data extraction, price trackers, CRM tools, dashboards, AI assistants on OpenAI or Claude.
Tell me what it has to do on the page. I'll tell you whether Manifest V3 permits it before you order.
Get to know Adeola Build Co
I take over where Lovable Replit and Base44 stop and ship your app to production
- FromGermany
- Member sinceJun 2026
- Avg. response time1 hour
Languages
German, English, Italian, French
FAQ
What happens if Google rejects it?
I fix it and resubmit at no charge. That's included, not an extra. Most rejections come back with a violation ID, and if I know the ID I know the fix. The point of building it properly the first time is that this rarely gets used.
Do I own the code, or am I renting it from you?
You own all of it. Full source, the manifest, the build config, and the repo. Nothing phones home to me, no license key, no dependency on anything I host. You can hand it to another developer tomorrow and they can build it without asking me a single question.
Can it do what I want, or will Manifest V3 block it?
Ask me before you order. MV3 killed some things that used to work, mainly blocking webRequest and any remotely loaded code. Most of what people want still works fine through declarativeNetRequest or content scripts. Tell me what it needs to do on the page and I'll tell you straight.
Do I need my own Chrome Web Store developer account?
Yes, and it should be in your company's name, not mine. There's a one-off Google fee for it. I'll walk you through creating it and then publish from your account, so the listing, the reviews and the users belong to you permanently.
Will it still work when Chrome updates?
Yes, and that's what MV3 is for. The version that broke everything is behind us. What actually breaks extensions is the site changing its HTML underneath a content script, so I write selectors defensively and tell you which ones are fragile.
Can you fix or take over an extension someone else built?
Yes, and half my work is that. The usual cause is MV2 code half-migrated to MV3, with a service worker written like a background page that loses state after thirty seconds. Send me the repo or the unpacked folder and I'll tell you what's wrong before you order.
