Growth idea action plan
Zoom Marketplace gallery shows the core workflow
Use the gallery to show the exact workflow the app unlocks, because Zoom review expects two to three images of real functionality rather than decorative product art.
Why this can grow a startup
A lot of listings still treat screenshots as branding leftovers. Zoom treats them like proof. The gallery guidance asks for two to three images that show what a user can expect with the integration, and it gives a specific image size of 1200 by 780 pixels. That pushes teams toward images that teach the workflow instead of generic marketing exports. When the screenshots show the setup or in-product path clearly, the listing becomes easier to review and easier for the buyer to trust.
Key metric to watch
Zoom asks for 2 to 3 gallery images at 1200 x 780 pixels and allows one optional video up to 40 MB.
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 zoom marketplace gallery shows the core workflow can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Brand channel.
- Use the evidence from developers.zoom.us 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
Zoom's rejection guide says the app gallery should include two to three images showing core features and functionality, with image resolution set to 1200 by 780 pixels.
Source: Zoom Developer Docs: Common reasons for app submission rejection (developers.zoom.us)
GrowthDex source hub: Zoom Developer Docs: Common reasons for app submission rejection
Last checked: 2026-06-05T03:25: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.
- Zoom Marketplace long description starts with audience fit same source · 2 shared channels
- Zoom Marketplace documentation covers add, use, and remove same source · 1 shared channel
- Zoom Marketplace short description as search snippet same source · 1 shared channel
- GitHub Marketplace feature card preview before brand refresh 3 shared channels
Related GrowthDex essays
- The Zoom Marketplace page should survive the first admin click marketplaces, brand trust, onboarding
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