VS Code extension icon, banner, and pricing remove listing ambiguity
Ship a proper icon, a deliberate gallery banner, and an honest pricing label so the listing does not look unfinished or commercially slippery.
Why this can grow a startup
The extension tile gets judged in seconds. If the icon looks generic, the banner clashes, and the pricing model only becomes clear after install, the page feels less trustworthy than the code might deserve. VS Code gives authors a small but useful presentation system in the manifest: the icon must meet a minimum size, the gallery banner can match the brand, and pricing has to be declared as Free or Trial. Those constraints are helpful because they force the commercial and visual surface to become explicit before the user clicks install.
Source-backed example
The VS Code manifest requires the icon path to point to an image of at least 128x128 pixels, supports galleryBanner formatting for the Marketplace header, and limits pricing values to Free or Trial.
Source-reported evidence
Source: Visual Studio Code Docs: Extension Manifest
VS Code requires an icon of at least 128x128 pixels and restricts pricing labels to Free or Trial.
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 Brand, Conversion, Marketplaces is relevant to developer tools, visual shelf, pricing clarity 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 Brand and Conversion, using evidence from Visual Studio Code Docs: Extension Manifest as context—not as a promised result.
- Record a baseline for: Qualified prospects who complete the intended paid 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.