Extension MVP
One browser, one job, live in the store.
from $900
from 2 weeks
- Chrome build on MV3
- The core feature, without scope drift
- Icons, screenshots, and listing copy
- Published and through review
Browser extensions
Browser extension development, end to end
You get a published extension in every store - built, packaged, illustrated, listed, and wired to an automated release pipeline. Not a zip of source with the store paperwork left to you.
- An MV3 extension at roughly 1M users, maintained and released across four stores
- Extensions built from scratch to roughly 50k combined store users
- Store-moderation incident response, including rejections and ban risk
What is included
Six stages. Most quotes cover the first two and stop there, which is where extension projects stall.
Manifest and architecture
MV3 from the start: service worker or event page, content-script boundaries, storage, and a permission set scoped to what review will actually approve.
One codebase, four browsers
Chrome, Edge, Opera, and Firefox from a single source tree, with per-browser manifest branches and the Firefox MV3 gaps handled up front rather than discovered after submission.
Promo assets
Icons, 1280x800 screenshots, promo tiles at 440x280, 920x680, and 1400x560, and a short demo video. Every store asks for a different set; you get all of them.
Listings and policy
Store copy, privacy policy, permission justifications, and data-usage disclosures written to match what the extension actually does.
Publishing and moderation
Submission in each store, review tracking, and rejection turnaround. A rejected listing is part of the job, not an extra.
Release automation
GitHub Actions: a per-browser build matrix, packaging, and upload through the Chrome Web Store, Edge Partner Center, and AMO APIs. Versioning and changelog included, so the next release is one tag.
Every store, not just Chrome
Four catalogues, four sets of asset requirements, four review queues.
Chrome Web Store
The strictest review. Permission justifications and a privacy policy are mandatory.
Edge Add-ons
Partner Center certification, its own asset sizes, a slower review cycle.
Firefox Add-ons
Human review with source submission for bundled builds, and an MV3 surface that differs from Chromium.
Opera Add-ons
A Chromium package, a separate catalogue, and its own moderation queue.
Packages
Fixed scope, fixed starting point. The scope of your extension moves the number, so treat these as a floor.
Full cycle
All four stores, the full asset kit, and automated releases.
from $2,400
from 4 weeks
- Chrome, Edge, Firefox, and Opera from one codebase
- Complete promo kit, demo video included
- Listings, privacy policy, permission justifications
- Publishing and moderation in every store
- GitHub Actions release automation
Care
An extension that is already live and has to stay live.
from $600 / month
monthly, cancel anytime
- Updates and small features
- MV3 and store policy changes
- Moderation incident response
- Release pipeline maintenance
Extension MVP
One browser, one job, live in the store.
Request a quote
from 2 weeks
- Chrome build on MV3
- The core feature, without scope drift
- Icons, screenshots, and listing copy
- Published and through review
Full cycle
All four stores, the full asset kit, and automated releases.
Request a quote
from 4 weeks
- Chrome, Edge, Firefox, and Opera from one codebase
- Complete promo kit, demo video included
- Listings, privacy policy, permission justifications
- Publishing and moderation in every store
- GitHub Actions release automation
Care
An extension that is already live and has to stay live.
Request a quote
monthly, cancel anytime
- Updates and small features
- MV3 and store policy changes
- Moderation incident response
- Release pipeline maintenance
Who builds it
Selim Ataballyev
Full-stack developer
I build the extensions myself. No agency layer, no handoff to a junior - you talk to the person writing the manifest, cutting the store assets, and answering the reviewer's rejection email. Most of what is on this page I have also run on my own extensions, which is how I know where the process breaks.
Track record
Extensions I have shipped and kept alive, not a list of technologies.
Legacy MV3 at roughly 1M users
An ageing extension with a large install base and a release process spread across four stores, each with its own review queue.
Maintained the MV3 codebase and ran the multi-store release, including the moderation incidents where a listing risked rejection or a ban.
The install base stayed intact through every release and policy change.
Extensions built from zero
New market segments the existing product could not reach.
Built and shipped new extensions from scratch, each with its own listing, assets, and store submissions.
Roughly 50k combined store users.
My own products
Everything above was inside a company. These are mine, end to end.
Several extensions of my own - written, published, and maintained solo, from the first commit to the store listing.
Every part of the pipeline on this page is one I run on my own releases.
Questions
How long does store review take?
Chrome is usually a few days, Edge and Opera can run longer, and Firefox involves a human reviewer. Plan for one to two weeks across all four, and longer for a first submission with broad permissions.
What happens if the extension is rejected?
I handle it. Rejections are normal, usually about permissions or an unclear privacy disclosure, and reworking the submission until it passes is part of the package rather than a change request.
Who owns the developer accounts and the source?
You do. The extension is published under your store accounts and the source is yours from the first commit. If the accounts do not exist yet, I set them up with you.
Can you migrate an existing MV2 extension?
Yes. That is a rewrite of the background layer, the permission model, and often the content scripts. It is scoped as its own project after I read the current codebase.
What happens after release?
Store policies and browser APIs keep moving, so an unattended extension eventually breaks. The Care package covers updates, policy changes, and moderation incidents; without it, you get the release pipeline and can run it yourself.
Do you build Safari extensions?
On request. Safari means an Xcode wrapper and App Store review, which is a different process from the four browsers above, so it is quoted separately.
Have an extension to build?
Tell me what it should do and which browsers matter. You get a scope, a number, and a timeline - not a discovery call.