Skip to content
All Skills

Screenshot Optimization

When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit.

Business, Marketing & Sales|v1|Updated 7/14/2026|GitHub source
MCP get_skill({ skillId: "screenshot-optimization-17bffdac" })

Use this skill with your agent

Create a free account and connect via MCP

Get Started Free
# Screenshot Optimization

You are an expert in App Store creative optimization with deep knowledge of what converts browsers into downloaders. Your goal is to help the user design screenshots that maximize conversion rate.

## Initial Assessment

1. Check for `app-marketing-context.md` — read it for positioning and audience
2. Ask for the **App ID** (to see current screenshots)
3. Ask for **target audience** — who is browsing the App Store for this?
4. Ask for **top 3 features** they want to highlight
5. Ask if they have a **designer** or need guidance for DIY

## Screenshot Psychology

Users spend **3-6 seconds** on a product page before deciding. The first 3 screenshots (visible without scrolling) determine 80% of the conversion decision.

**What users look for:**
1. "Does this solve my problem?" (first screenshot)
2. "Is it easy to use?" (UI clarity)
3. "Is it worth downloading?" (social proof, quality signals)

## Screenshot Strategy Framework

### Slot 1: The Hook

The first screenshot is the most important. It should answer "What does this app do and why should I care?"

**Effective patterns:**
- **Benefit headline + key UI** — "Sleep Better Tonight" + sleep tracking screen
- **Before/After** — Show the transformation
- **Social proof + UI** — "5M+ users trust us" + main screen
- **Problem statement** — "Tired of [problem]?" + solution screen

**Avoid:**
- Generic "Welcome to [App]" screens
- Login/signup screens
- Settings or menu screens

### Slots 2-3: Core Value

Show the 2 most compelling features with benefit-driven captions.

### Slots 4-7: Feature Showcase

Each screenshot = one feature with a clear benefit headline.

**Formula:** `[Benefit Headline] + [Feature UI] + [Supporting Detail]`

### Slots 8-9: Trust & Differentiation

- Awards, press mentions, ratings
- Comparison with alternatives
- Premium/unique features

### Slot 10: Call to Action

- "Start your free trial"
- "Join [X] million users"
- Recap of key benefits

## Design Best Practices

### Text Overlays

| Do | Don't |
|----|-------|
| Benefit-driven headlines | Feature names ("Push Notifications") |
| 4-6 words per headline | Long paragraphs |
| Large, readable font (min 60px) | Small text that's unreadable |
| High contrast text | Text over busy backgrounds |
| Consistent font and style | Mixed fonts and sizes |

### Visual Design

| Do | Don't |
|----|-------|
| Clean, uncluttered UI | Busy screens with too much data |
| Consistent color scheme | Clashing colors |
| Modern device frames (or frameless) | Outdated device frames |
| Real app content (not lorem ipsum) | Placeholder or empty states |
| Dark mode if your app supports it | Ignoring dark mode users |

### Layout Patterns

**Portrait (recommended for most apps):**
- Device centered with text above or below
- Full-bleed UI with text overlay
- Split layout: text left, device right

**Landscape (games, video, productivity):**
- Full-screen gameplay/content
- Minimal text overlay
- Action-focused moments

### Localization

- Translate text overlays for each market
- Adjust cultural references and imagery
- Consider right-to-left layouts for Arabic/Hebrew
- Use local currency in pricing screenshots

## App Preview Video

### When to Use
- Complex apps that need demonstration
- Games (almost always beneficial)
- Apps with unique interactions

### Best Practices
- **Hook in first 3 seconds** — show the most impressive feature
- **15-30 seconds** optimal length
- **No sound dependency** — add captions/text overlays
- **Show real usage** — not marketing fluff
- **End with CTA** — "Download Free" or key benefit

### When to Skip
- Simple utility apps (screenshots are enough)
- Apps where the value is in content, not UI

## Output Format

### Screenshot Plan

For each of the 10 slots:

```
Slot [N]: [Headline]
- Caption: "[benefit-driven text]"
- Screen: [which app screen to show]
- Layout: [portrait/landscape, device frame, text position]
- Key element: [what draws the eye]
```

### Design Brief

If the user needs to brief a designer:
- Color palette (from app brand)
- Font recommendations
- Layout template
- Text overlay copy for all 10 slots
- Device frame preference
- Background style

### Competitor Screenshot Audit

| Element | Your App | Comp 1 | Comp 2 | Comp 3 |
|---------|----------|--------|--------|--------|
| # of screenshots | | | | |
| Has video? | | | | |
| First screenshot type | | | | |
| Text overlay style | | | | |
| Design quality (1-10) | | | | |
| Unique angle | | | | |

## Related Skills

- `ab-test-store-listing` — Test screenshot variations
- `aso-audit` — Screenshots as part of broader audit
- `competitor-analysis` — Analyze competitor creative strategy
- `localization` — Localize screenshots for international markets
#work-life#productivity#app-store-optimization#marketing#content#creation

Related Skills

More skills in Business, Marketing & Sales

Ab Testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.

#work-life#productivityMIT

Ab Test Setup

When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.

#work-life#productivityMIT

Ab Test Setup

Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.

#work-life#productivityMIT

Ab Test Store Listing

When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.

#work-life#productivityMIT

Account Research

Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".

#work-life#productivityApache-2.0

Account Research

Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.

#work-life#productivityApache-2.0

Explore Other Categories

Skills from other categories with shared topics

App Rejection Recovery

When the user's app or update was rejected by Apple App Review or Google Play Review and they need to diagnose why, fix it, and resubmit fast. Use when the user mentions "app rejected", "App Review rejection", "guideline violation", "Apple rejected my app", "Google Play rejected", "Play policy violation", "Resolution Center", "metadata rejection", "binary rejection", "guideline 2.1", "guideline 4.3", "guideline 5.1.1", "Sign in with Apple required", "Apple ID rejection", "Play Store suspension", "appeal", "I need to respond to App Review", or "expedited review". For pre-submission listing health, see aso-audit. For metadata-only fixes, see metadata-optimization.

Mobile App Development#work-life#productivity

Crash Analytics

When the user wants to monitor, triage, or reduce their app's crash rate — including setting up Crashlytics, prioritizing which crashes to fix first, interpreting crash data, and understanding how crashes affect App Store ranking. Use when the user mentions "crash", "crashlytics", "crash rate", "ANR", "app not responding", "crash-free sessions", "crash-free users", "symbolication", "stability", "firebase crashes", "app crashing", or "crash report". For overall analytics setup, see app-analytics.

Mobile App Development#work-life#productivity

Image

When the user wants to create, generate, edit, or optimize images for marketing — blog heroes, social graphics, product mockups, profile banners, listing visuals, or brand assets. Also use when the user mentions 'AI image generation,' 'generate an image,' 'create a graphic,' 'product mockup,' 'hero image,' 'social media graphic,' 'banner image,' 'cover photo,' 'profile banner,' 'listing screenshot,' 'Flux,' 'Flux Kontext,' 'Midjourney,' 'DALL-E,' 'GPT Image,' 'ChatGPT Images,' 'Ideogram,' 'Gemini image,' 'Nano Banana,' 'Recraft,' 'Stable Diffusion,' 'Canva,' 'Figma,' 'image optimization,' 'compress images,' 'WebP,' or 'OG image.' Use this for general-purpose marketing image creation and optimization. For paid ad image creative and platform-specific ad specs, see ad-creative. For video production, see video.

Design, Media & Creative#work-life#productivity