# Firefox Add-ons source package with build steps before review

> Prepare the reviewable source package and build instructions before submission, because Mozilla can reject or block the add-on when reviewers cannot reproduce what shipped.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/firefox-add-ons-source-package-with-build-steps-before-review/
- Source: [extensionworkshop.com](https://extensionworkshop.com/documentation/publish/add-on-policies/)
- GrowthDex source hub: [Firefox Extension Workshop: Add-on Policies](/sources/firefox-extension-workshop-add-on-policies-extensionworkshop-com/)
- Last checked: 2026-06-06T12:04:00Z
- Rarity: rare
- Budget: low
- Channels: Marketplaces, Operations, Engineering
- Stages: browser extensions, firefox add-ons, review ops, build discipline


## Why this can grow

Review drag is often self-inflicted. Teams submit a polished package, then scramble when the reviewer asks how the build works or where the readable source lives. Mozilla's policy is blunt: reviewers need the source before transpilation or minification, plus build reproduction steps, and failure to provide them can lead to rejection or blocking. The practical upside is bigger than passing review. A review-ready build usually means the extension team has cleaner release discipline, clearer dependency control, and less mystery in the product they are asking users to trust.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where firefox add-ons source package with build steps before review can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Operations channel.
3. Use the evidence from extensionworkshop.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Mozilla requires reviewable source code, build reproduction instructions, and supported dependency paths during submission, and says failure to provide that information results in rejection or blocking.

## Adjacent tactics in the same lane

- [Firefox Add-ons no-surprises copy before install](/growth-ideas/firefox-add-ons-no-surprises-copy-before-install/) - same source, 1 shared channel, 2 shared stages
- [Firefox Add-ons paid function disclosed on listing](/growth-ideas/firefox-add-ons-paid-function-disclosed-on-listing/) - same source, 1 shared channel, 2 shared stages
- [Chrome Web Store partial rollout after 10,000 active users](/growth-ideas/chrome-web-store-partial-rollout-after-10000-active-users/) - 2 shared channels, 1 shared stage
- [WordPress plugin Stable Tag, tag folder, and PHP version stay in sync](/growth-ideas/wordpress-plugin-stable-tag-tag-folder-and-php-version-stay-in-sync/) - 3 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The Firefox Add-ons page should remove the surprise before install](/blog/the-firefox-add-ons-page-should-remove-the-surprise-before-install/) - marketplaces, SEO, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.