Growth idea action plan
VS Code extension verified publisher and pre-release track
Earn the verified publisher badge, then use the built-in pre-release track for sharper feedback instead of surprising the stable install base.
Why this can grow a startup
A lot of extension teams mix two different jobs together: proving who they are and testing what is new. VS Code gives a cleaner split. Verified publisher status adds a trust signal tied to domain ownership and time in good standing, while the pre-release channel gives risk-tolerant users a place to try newer builds. The pre-release rules are specific enough to matter operationally: version numbers must stay distinct, pre-release support starts at VS Code 1.63.0, and the docs recommend odd and even release tracks. That makes experimentation feel deliberate instead of chaotic.
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 vs code extension verified publisher and pre-release track can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Trust and Retention channel.
- Use the evidence from code.visualstudio.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
VS Code's publishing guide says verified publisher status requires at least one Marketplace extension for six months and a domain registration that is also at least six months old. The same guide says pre-release extensions should use the --pre-release flag, keep distinct versions, and set engines.vscode to >= 1.63.0.
Source: Visual Studio Code Docs: Publishing Extensions (code.visualstudio.com)
GrowthDex source hub: Visual Studio Code Docs: Publishing Extensions
Last checked: 2026-06-06T12:40:00Z
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- VS Code extension README and CHANGELOG finish the detail page same source · 1 shared channel · 1 shared stage
- Chrome Web Store partial rollout after 10,000 active users 2 shared channels
- Firefox approved-version rollback within 24 hours 2 shared channels
- JetBrains plugin hidden release before public launch 1 shared channel · 1 shared stage
Related GrowthDex essays
- The VS Code extension page should finish the trust check marketplaces, SEO, brand trust
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