Teams Store icon parity with 32px name legibility
Keep the color icon, outline icon, marketplace icon, and abbreviated mark aligned so the brand still reads at Teams' smallest size.
Why this can grow a startup
Store branding fails when the small assets stop matching the product memory. Microsoft makes the rule concrete. The color and outline icon must match, the marketplace icon must match the color icon in the package, and long words should be abbreviated so the mark stays readable when resized to 32 by 32. That matters because enterprise buyers often scan a grid before they read a paragraph. If the small mark is inconsistent or illegible, the listing looks less trustworthy before the copy gets a chance to help.
Source-backed example
Microsoft's Teams Store icon guidance says the listing must include matching color and outline PNG icons, the marketplace icon in Partner Center must match the package icon, and long app names should be abbreviated so the icon stays readable at 32 by 32.
Source-reported evidence
Source: Microsoft Learn: Teams app icon for Teams Store and app bar
Teams uses a 192x192 color icon and a 32x32 outline icon, and Microsoft recommends abbreviating long words for 32x32 readability.
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, Brand, Trust is relevant to teams store, icon system, brand consistency 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 Marketplaces and Brand, using evidence from Microsoft Learn: Teams app icon for Teams Store and app bar 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
Choose the first market, local proof, partners, and distribution sequence with operator context.