VS Code extension category picks the right shelf
Choose the narrowest allowed category instead of dumping the extension into a generic bucket, because VS Code users browse and filter by category before they trust a new publisher.
Why this can grow a startup
Categories look administrative until you remember how people actually browse the Extensions view. A lot of users start with a language, tool type, or workflow shelf and trim the list from there. The Marketplace docs explicitly support category filters in the extensions view, while the manifest limits publishers to a fixed set of category values. That turns category selection into positioning. A formatter that hides in Other or a testing tool that pretends to be general utility makes the page harder to find and harder to understand.
Source-backed example
The extension manifest lists fixed category values such as Programming Languages, Linters, Formatters, Testing, Data Science, and Machine Learning, and the VS Code extensions guide says users can filter the Marketplace by extension category.
Source-reported evidence
Source: Visual Studio Code Docs: Use Extensions in VS Code
VS Code lets users filter the Extensions view by category, while the manifest constrains publishers to a fixed category 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 Marketplaces, SEO, Brand is relevant to developer tools, category fit, marketplace positioning 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 Marketplaces and SEO, using evidence from Visual Studio Code Docs: Use Extensions in VS Code as context—not as a promised result.
- Record a baseline for: Qualified search visitors who complete the 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.