app-store-screenshots

Création de captures d'écran pour l'App Store et Google Play avec les spécifications exactes des plateformes. Couvre les dimensions iOS/Android, l'ordre de la galerie, les maquettes d'appareils et les vidéos de prévisualisation. Utilisation pour : optimisation de l'App Store, ASO, captures d'écran d'applications, prévisualisation d'applications, fiche Play Store. Déclencheurs : captures d'écran App Store, aso, optimisation App Store, captures d'écran Play Store, prévisualisation d'application, fiche d'application, captures d'écran iOS, captures d'écran Android, images App Store, maquette d'application, maquette d'appareil, galerie d'application, fiche de store

npx skills add https://github.com/halt-catch-fire/skills --skill app-store-screenshots

Install the belt CLI skill: npx skills add belt-sh/cli

App Store Screenshots

Create app store screenshots and preview videos via inference.sh CLI.

Quick Start

Requires inference.sh CLI (belt). Install instructions

belt login

# Generate a device mockup scene
belt app run falai/flux-dev-lora --input '{
  "prompt": "iPhone 15 Pro showing a clean modern app interface with analytics dashboard, floating at slight angle, soft gradient background, professional product photography, subtle shadow, marketing mockup style",
  "width": 1024,
  "height": 1536
}'

Platform Specifications

Apple App Store (iOS)

DeviceDimensions (px)Required
iPhone 6.7" (15 Pro Max)1290 x 2796Required
iPhone 6.5" (11 Pro Max)1284 x 2778Required
iPhone 5.5" (8 Plus)1242 x 2208Optional
iPad Pro 12.9" (6th gen)2048 x 2732If iPad app
iPad Pro 11"1668 x 2388If iPad app
  • Up to 10 screenshots per localization
  • First 3 screenshots are visible without scrolling (critical)
  • Formats: PNG or JPEG (no alpha/transparency for JPEG)

Google Play Store (Android)

SpecValue
Min dimensions320 px (any side)
Max dimensions3840 px (any side)
Aspect ratio16:9 or 9:16
Max screenshots8 per device type
FormatsPNG or JPEG (24-bit, no alpha)
  • Feature graphic: 1024 x 500 px (required for featuring)
  • Promo video: YouTube URL (optional but recommended)

The First 3 Rule

80% of App Store impressions show only the first 3 screenshots (before the user scrolls). These three must:

  1. Communicate the core value proposition
  2. Show the best feature/outcome
  3. Differentiate from competitors

Screenshot Gallery Order

PositionContentPurpose
1Hero — core value, best featureStop the scroll, communicate what the app does
2Key differentiatorWhat makes you unique vs competitors
3Most popular featureThe thing users love most
4Social proof or outcomeRatings, results, testimonials
5-8Additional featuresSupporting features, settings, integrations
9-10Edge casesSpecialized features for niche users

Screenshot Styles

1. Device Frame with Caption

The standard: device mockup showing the app, caption text above/below.

┌──────────────────────────┐
│   "Track Your Habits     │  ← Caption (benefit-focused)
│    Effortlessly"         │
│                          │
│   ┌──────────────────┐   │
│   │                  │   │
│   │   App Screen     │   │  ← Actual app UI in device frame
│   │   Content        │   │
│   │                  │   │
│   │                  │   │
│   └──────────────────┘   │
│                          │
└──────────────────────────┘

2. Full-Bleed UI (No Device Frame)

The app UI fills the entire screenshot. Works for immersive apps.

3. Lifestyle Context

The device shown in a real-world context (person holding phone, on desk, etc.).

4. Feature Highlight with Callouts

UI screenshot with arrows/circles pointing to specific features.

Caption Writing

Rules

  • Max 2 lines of text
  • Benefit-focused, not feature-focused
  • 30pt+ equivalent font size (must be readable in store)

Examples

❌ Feature-focused:
"Push Notification System"
"Calendar View with Filters"
"Data Export Functionality"

✅ Benefit-focused:
"Never Miss a Deadline Again"
"See Your Week at a Glance"
"Share Reports in One Tap"

Generating Screenshots

Hero Screenshot (Position 1)

# Clean device mockup with hero feature
belt app run falai/flux-dev-lora --input '{
  "prompt": "modern iPhone showing a beautiful fitness tracking app with activity rings and workout summary, device floating at slight angle against soft purple gradient background, professional product shot, clean minimal composition, subtle reflection",
  "width": 1024,
  "height": 1536
}'

Feature Highlight

# Feature callout style
belt app run bytedance/seedream-4-5 --input '{
  "prompt": "app store screenshot style, iPhone showing a messaging app with AI writing suggestions highlighted, clean white background, subtle UI callout arrows, professional marketing asset, modern design",
  "size": "2K"
}'

Lifestyle Context

# Device in real-world setting
belt app run falai/flux-dev-lora --input '{
  "prompt": "person holding iPhone showing a cooking recipe app, kitchen background with ingredients, warm natural lighting, over-the-shoulder perspective, lifestyle photography, authentic feeling",
  "width": 1024,
  "height": 1536
}'

Before/After

# Split comparison
belt app run infsh/stitch-images --input '{
  "images": ["before-screenshot.png", "after-screenshot.png"],
  "direction": "horizontal"
}'

Preview Videos

Apple App Store

SpecValue
Duration15-30 seconds
OrientationPortrait or landscape (match app)
AudioOptional (loops silently in store)
FormatH.264, .mov or .mp4

Google Play

SpecValue
SourceYouTube URL
Duration30s-2min recommended
OrientationLandscape preferred

Preview Video Structure

SegmentDurationContent
Hook0-3sShow the core outcome/wow moment
Feature 13-10sDemonstrate top feature in action
Feature 210-18sSecond key feature
Feature 318-25sThird feature or social proof
CTA25-30sEnd screen with app icon
# Generate preview video scenes
belt app run google/veo-3-1-fast --input '{
  "prompt": "smooth screen recording style, finger tapping on a modern mobile app interface, swiping between screens showing charts and data visualizations, clean UI transitions, professional app demo"
}'

Localization

Each language gets its own set of screenshots. Priorities:

MarketLocalization Level
Primary marketsFull: new screenshots + translated captions
Secondary marketsTranslated captions, same screenshots
OtherEnglish defaults

Key localization markets: English, Japanese, Korean, Chinese (Simplified), German, French, Spanish, Portuguese (Brazilian)

A/B Testing (Google Play)

Google Play Console supports store listing experiments:

  • Test different screenshot orders
  • Test with/without device frames
  • Test different captions
  • Test different color schemes
  • Run for 7+ days with 50%+ traffic for significant results

Common Mistakes

MistakeProblemFix
Settings screen as screenshotNobody cares about settingsShow core value, not infrastructure
Onboarding flow screenshotsShows friction, not valueShow the app in-use state
Too much textUnreadable in storeMax 2 lines, 30pt+ font
Wrong dimensionsRejected by storeUse exact platform specs
All screenshots look the sameNo reason to scrollVary composition and content
Feature-focused captionsDoesn't communicate benefit"Never Miss a Deadline" > "Push Notifications"
Outdated UILooks abandonedUpdate screenshots with each major release
No hero screenshotWeak first impressionPosition 1 = your best shot

Checklist

  • Correct dimensions for target platform
  • First 3 screenshots communicate core value
  • Captions are benefit-focused, max 2 lines
  • No onboarding or settings screens
  • Preview video is 15-30s with hook in first 3s
  • Localized for top markets
  • Feature graphic (1024x500) for Google Play
  • Screenshots updated for current app version
  • A/B test variant prepared

Related Skills

npx skills add inference-sh/skills@ai-image-generation
npx skills add inference-sh/skills@ai-video-generation
npx skills add inference-sh/skills@image-upscaling
npx skills add inference-sh/skills@prompt-engineering

Browse all apps: belt app list

Plus de skills de halt-catch-fire

ai-image-generation
halt-catch-fire
Générez des images IA avec GPT-Image-2, FLUX, Gemini, Grok, Seedream, Reve et plus de 50 modèles via l'interface CLI inference.sh. Modèles : GPT-Image-2, FLUX Dev LoRA, FLUX.2 Klein LoRA, Gemini 3 Pro Image, Grok Imagine, Seedream 4.5, Reve, ImagineArt. Capacités : texte vers image, image vers image, inpainting, LoRA, édition d'image, upscaling, rendu de texte. Utilisation pour : art IA, maquettes de produits, concept art, graphiques pour réseaux sociaux, visuels marketing, illustrations. Déclencheurs : flux, génération d'image, image IA, texte vers...
creativemediaimage
ai-video-generation
halt-catch-fire
We need to translate the given text from English to French. The text describes an AI video generation skill. We must preserve the name "ai-video-generation" but it's not in the text, so we ignore. Preserve product names, protocol names, URLs, numbers, technical terms. So "Google Veo", "Seedance 2.0", "HappyHorse", "Wan", "Grok", "inference.sh CLI", "Veo 3.1", "Veo 3", "Seedance 2.0", "HappyHorse 1.0", "Wan 2.5", "Grok Imagine Video", "OmniHuman", "Fabric", "HunyuanVideo", "text-to-video", "image-to-video", "reference-to-video", "video editing", "lipsync", "avatar animation", "video upscaling", "foley sound", "social media videos", "marketing content", "explainer videos", "product demos", "AI avatars",
creativevideomedia
twitter-automation
halt-catch-fire
Automatisez Twitter/X avec publication, engagement et gestion des utilisateurs via l'interface CLI inference.sh. Applications : x/post-tweet, x/post-create (avec média), x/post-like, x/post-retweet, x/dm-send, x/user-follow. Capacités : publier des tweets, planifier du contenu, aimer des publications, retweeter, envoyer des messages directs, suivre des utilisateurs, obtenir des profils. Utilisation pour : automatisation des réseaux sociaux, planification de contenu, bots d'engagement, croissance d'audience, API X. Déclencheurs : twitter api, x api, tweet automation, post to twitter, twitter bot, social media automation, x...
marketingapicommunication
ai-avatar-video
halt-catch-fire
We need to translate the given text from English to French, preserving the name "ai-avatar-video" and other technical terms. The text describes creating AI avatar and talking head videos via inference.sh CLI. It recommends P-Video-Avatar, and lists other options: OmniHuman, Fabric, PixVerse. Audio options: Inworld TTS-2, ElevenLabs, Kokoro. Capabilities: audio-driven avatars, text-to-avatar, lipsync videos, talking head generation, virtual presenters, UGC content. Use for: AI presenters, explainer videos, virtual influencers, dubbing, marketing videos, UGC ads, gaming avatars,... We must not include the name "ai-avatar-video" unless it appears in the source text. It does not appear in the source text, so we omit it. We translate the rest naturally. Keep product names, protocol names, URLs, numbers, technical terms as is. So "inference.sh CLI" stays, "P-Video-Avatar", "OmniHuman", "F
videocreativemedia
agent-browser
halt-catch-fire
Automatisation de navigateur pour agents IA via inference.sh. Naviguer sur des pages web, interagir avec des éléments en utilisant les références @e, prendre des captures d'écran, enregistrer des vidéos. Capacités : scraping web, remplissage de formulaires, clics, saisie, glisser-déposer, téléchargement de fichiers, exécution JavaScript. Utilisation pour : automatisation web, extraction de données, tests, navigation agent, recherche. Déclencheurs : navigateur, automatisation web, scraping, navigation, clic, remplissage de formulaire, capture d'écran, navigation web, playwright, navigateur headless, agent web, surf internet, enregistrement vidéo
browser-automationweb-scrapingtesting
web-search
halt-catch-fire
Recherche web et extraction de contenu avec Tavily et Exa via l'interface en ligne de commande inference.sh. Applications : Tavily Search, Tavily Extract, Exa Search, Exa Answer, Exa Extract. Capacités : recherche assistée par IA, extraction de contenu, réponses directes, recherche documentaire. Utilisation pour : recherche, pipelines RAG, vérification des faits, agrégation de contenu, agents. Déclencheurs : recherche web, tavily, exa, api de recherche, extraction de contenu, recherche, recherche internet, recherche IA, assistant de recherche, scraping web, rag, alternative à perplexity
researchweb-scrapingapi
infsh-cli
halt-catch-fire
We need to translate the given text from English to French, preserving the name "infsh-cli" and other technical terms, product names, protocol names, URLs, numbers, etc. The instruction says: "Do not include the name unless it appears in the source text." The name "infsh-cli" is not in the source text, so we don't include it. The source text has "inference.sh CLI" - that should be preserved as is? The instruction says preserve product names, so "inference.sh CLI" should stay. Also "FLUX, Veo, Gemini, Grok, Claude, Seedance, OmniHuman, Tavily, Exa, OpenRouter" are product names, keep them. "Twitter" is a product name. "AI" is a term, keep as is or translate? Usually "IA" in French, but the instruction says preserve technical terms? "AI" is a common acronym, often kept as is. But in French, "IA" is used. However, the instruction says "preserve product names
developmentapicreative
landing-page-design
halt-catch-fire
We need to translate the given text from English to French. The text is a description of an agent skill for landing page design. We must preserve the name "landing-page-design" but it's not in the text, so we don't include it. We translate only the text inside <text>. No extra labels. Keep technical terms like "CTA", "F-pattern", "SaaS", etc. as is or translate if appropriate? The instruction says preserve technical terms, so "CTA" stays, "F-pattern" might be kept or translated? Usually "F-pattern" is a known term, but in French it might be "motif en F" or keep as is. Since it's a technical term, I'll keep "F-pattern" as is. "above-the-fold" is a term, often kept as "above-the-fold" or "au-dessus de la ligne de flottaison". I'll keep as "above-the-fold" for consistency. "social proof" -> "preuve sociale". "mobile design" -> "conception mobile