Firefox add-on ID in manifest before session-dependent APIs
Set the Firefox add-on ID in `manifest.json` early if the extension depends on stable identity, because temporary IDs reset across sessions and break more than most teams expect.
Why this can grow a startup
A lot of extension teams discover the add-on ID too late, after sync, redirect, or native-messaging behavior starts acting haunted in development. Mozilla's guidance is useful because it turns the ID into an early architecture choice instead of a release footnote. When the ID is set from the start, the same extension identity can survive development, signing, and production updates. That makes debugging cleaner and keeps session-dependent flows from changing shape every time Firefox restarts.
Source-backed example
Firefox Extension Workshop recommends defining an extension ID in `manifest.json` when development begins, requires a Manifest V3 extension ID before submission to AMO, and notes that temporary IDs change when Firefox restarts if no ID is defined.
Source-reported evidence
Source: Firefox Extension Workshop: Extensions and the add-on ID
Manifest V3 add-ons must define an ID before AMO submission, and temporary Firefox IDs change after restart when no ID is set.
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 Product, Developer Experience, Retention is relevant to browser extensions, firefox add-ons, manifest architecture and you can run a bounded test with a free 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 Product and Developer Experience, using evidence from Firefox Extension Workshop: Extensions and the add-on ID 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
Connect activation, customer value, retention, and referral into one measurable loop.