Growth idea action plan
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.
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
- Define one narrow startup segment where firefox add-on id in manifest before session-dependent apis can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Product and Developer Experience channel.
- Use the evidence from extensionworkshop.com to set the first version of the message, format, and audience.
- Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
- Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.
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: Firefox Extension Workshop: Extensions and the add-on ID (extensionworkshop.com)
GrowthDex source hub: Firefox Extension Workshop: Extensions and the add-on ID
Last checked: 2026-06-07T05:06:41.503Z
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Firefox approved-version rollback within 24 hours 1 shared channel · 2 shared stages
- AI response rating with follow-up context 2 shared channels
- Churned-account request alert view with Slack notifications 2 shared channels
- Customer page subscription for request lifecycle signals 2 shared channels
Related GrowthDex essays
- The extension page should survive the update, not just the install brand trust, retention, SEO
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
Why this is worth your time
GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.
Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% across 6 Southeast Asian markets.
Want help turning this into a growth system?
If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.
Work with Ian on growth advisory