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.
Why this can grow a startup
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.
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.
Source-reported evidence
Source: Firefox Extension Workshop: Add-on Policies · Browse Firefox Extension Workshop: Add-on Policies tactics
Mozilla states that missing reviewable source code or build instructions can result in rejection or blocking.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Marketplaces, Operations, Engineering is relevant to browser extensions, firefox add-ons, review ops and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Marketplaces and Operations, using evidence from Firefox Extension Workshop: Add-on Policies as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.
SOURCE HUB
More tactics from Firefox Extension Workshop: Add-on Policies
Explore related GrowthDex examples and evidence connected to Firefox Extension Workshop: Add-on Policies.
Open Firefox Extension Workshop: Add-on Policies source hub