# Safari extension in-use screenshots, not title art

> Show the extension working instead of leaning on splash art or login chrome, because Apple reviews screenshots as product proof rather than poster design.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/safari-extension-in-use-screenshots-not-title-art/
- Source: [developer.apple.com](https://developer.apple.com/app-store/review/guidelines/)
- GrowthDex source hub: [Apple Developer: App Review Guidelines](/sources/apple-developer-app-review-guidelines-developer-apple-com/)
- Last checked: 2026-06-07T00:42:16Z
- Rarity: uncommon
- Budget: free
- Channels: Marketplaces, Brand, Conversion
- Stages: browser extensions, safari extensions, review trust, visual proof


## Why this can grow

A lot of thin extension pages try to look polished by filling the gallery with title cards, marketing art, or the login screen. Apple’s review rule cuts through that quickly: screenshots should show the app in use, not merely title art, login pages, or splash screens. That is a better growth rule than it sounds. Real in-use screenshots reduce guesswork. They tell the buyer what the extension changes in the browser, how it behaves on the page, and whether the tool looks mature enough to trust. Decorative gallery assets may feel branded, but they usually leave the hardest conversion question unanswered.

## 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

1. Define one narrow startup segment where safari extension in-use screenshots, not title art can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Brand channel.
3. Use the evidence from developer.apple.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Apple’s App Review Guidelines say screenshots should show the app in use and not merely title art, login pages, or splash screens.

## Adjacent tactics in the same lane

- [Firefox Add-ons no-surprises copy before install](/growth-ideas/firefox-add-ons-no-surprises-copy-before-install/) - 3 shared channels, 1 shared stage
- [Firefox Add-ons paid function disclosed on listing](/growth-ideas/firefox-add-ons-paid-function-disclosed-on-listing/) - 2 shared channels, 2 shared stages
- [Safari extension Extensions category is a real shelf](/growth-ideas/safari-extension-extensions-category-is-a-real-shelf/) - 2 shared channels, 2 shared stages
- [Safari extension first three screenshots show the enable path](/growth-ideas/safari-extension-first-three-screenshots-show-the-enable-path/) - 2 shared channels, 2 shared stages

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The Safari extension page should finish the setup before the install](/blog/the-safari-extension-page-should-finish-the-setup-before-the-install/) - marketplaces, SEO, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.