screenshot-optimization
eronred/aso-skills
Design and optimize App Store screenshots and preview videos to maximize conversion.
What is screenshot-optimization?
Expert guidance on creating high-converting App Store screenshots and preview videos. Use this when designing, evaluating, or optimizing creative assets for app product pages. Covers psychology, strategy, design best practices, and competitor analysis.
- Assess current screenshots and identify conversion gaps
- Develop a 10-slot screenshot strategy with benefit-driven headlines and layouts
- Provide design best practices for text overlays, visual hierarchy, and localization
- Create app preview video recommendations and timing guidance
- Audit competitor screenshots to identify differentiation opportunities
- Generate design briefs for designers or DIY guidance
How to install screenshot-optimization
npx skills add https://github.com/eronred/aso-skills --skill screenshot-optimization- App ID (to view current screenshots)
- Target audience definition
- Top 3 features to highlight
- Access to app screenshots or design tools
How to use screenshot-optimization
- 1.Check for app-marketing-context.md to understand positioning and audience
- 2.Provide your App ID so current screenshots can be reviewed
- 3.Define your target audience and their primary pain point
- 4.List your top 3 features you want to highlight
- 5.Decide if you have a designer or need DIY guidance
- 6.Receive a 10-slot screenshot plan with specific headlines, layouts, and design recommendations
- 7.(Optional) Get a competitor screenshot audit to identify differentiation opportunities
- 8.(Optional) Request a design brief to hand off to a designer
Use cases
- Planning a complete screenshot redesign to improve conversion rate
- Optimizing the critical first 3 screenshots that determine 80% of conversion decisions
- Creating localized screenshots for international App Store markets
- Designing app preview videos that hook users in the first 3 seconds
- Auditing competitor creative strategies to find unique positioning angles
- App developers and product managers launching or relaunching apps
- Mobile app marketers focused on App Store optimization (ASO)
- Designers creating App Store creative assets
- Growth teams running app install campaigns
- Indie developers managing their own app marketing
screenshot-optimization FAQ
The first screenshot is critical—it has 3-6 seconds to answer 'Does this solve my problem?' and determines 80% of conversion decisions. Use benefit-driven headlines, social proof, or before/after patterns rather than generic welcome screens.
The framework recommends 10 slots: 1 hook, 2-3 core value, 4-7 feature showcase, 8-9 trust/differentiation, and 10 call-to-action. However, start with the first 3 (most visible without scrolling) and expand based on your app complexity.
Yes, if your app has complex interactions, is a game, or has unique features that need demonstration. Skip it for simple utility apps where screenshots suffice. Keep videos 15-30 seconds with a hook in the first 3 seconds.
Translate text overlays, adjust cultural references and imagery, consider right-to-left layouts for Arabic/Hebrew, and use local currency in pricing screenshots. Create market-specific versions rather than one-size-fits-all designs.
Use the ab-test-store-listing skill to A/B test screenshot variations. Track conversion rate changes, install volume, and user feedback. Compare your design against competitors using the competitor screenshot audit framework.
Full instructions (SKILL.md)
Source of truth, from eronred/aso-skills.
name: screenshot-optimization description: 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. metadata: version: 1.0.0
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
- Check for
app-marketing-context.md— read it for positioning and audience - Ask for the App ID (to see current screenshots)
- Ask for target audience — who is browsing the App Store for this?
- Ask for top 3 features they want to highlight
- 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:
- "Does this solve my problem?" (first screenshot)
- "Is it easy to use?" (UI clarity)
- "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 variationsaso-audit— Screenshots as part of broader auditcompetitor-analysis— Analyze competitor creative strategylocalization— Localize screenshots for international markets
Related skills
More from eronred/aso-skills and the wider catalog.
seasonal-aso
When the user wants to optimize their App Store listing for seasonal events, holidays, or trending moments — including keyword opportunities, metadata updates, screenshot theming, and timing strategy. Use when the user mentions "seasonal", "holiday", "Christmas", "New Year", "Valentine's Day", "summer", "back to school", "seasonal keywords", "trending now", "limited time", or wants to capitalize on a calendar event. For general keyword research, see keyword-research. For full metadata rewrites, see metadata-optimization.
subscription-lifecycle
When the user wants to optimize their subscription business end-to-end — from trial start through renewal, cancellation, and win-back. Use when the user mentions "subscription lifecycle", "trial conversion", "churn", "cancellation", "win-back", "lapsed subscribers", "dunning", "billing retry", "grace period", "renewal rate", "subscriber LTV", or "resubscribe". For paywall design and pricing strategy, see monetization-strategy. For subscription analytics dashboards, see app-analytics.
ua-campaign
Plan and optimize paid user acquisition campaigns across Apple Search Ads, Meta, Google UAC, TikTok, and more.
web-to-app-funnel
When the user wants to design or optimize the funnel that takes web visitors into installing and onboarding the app — including smart app banners, web-to-app deep links, deferred deep links, web onboarding (Stripe-paid web flow before app install), QR codes, "open in app" CTAs, and the trade-off between paying on web vs in-app. Use when the user mentions "web to app", "smart app banner", "Stripe before app", "web paywall before install", "Branch web SDK", "web funnel for app", "AppsFlyer OneLink web", "Universal Links", "App Links", "QR code to app", "open in app", "deferred deep link from web", or "should I sell on web first then push to app". For pure in-app onboarding, see onboarding-optimization. For deep link infra, see attribution-setup.
ce-agent-native-architecture
Build applications where agents are first-class citizens using atomic tools and prompt-defined features.
ce-agent-native-audit
Comprehensive agent-native architecture review with scored principles across 8 core dimensions