app-store-screenshots

tarafından halt-catch-fire

We need to translate the given text from English to Turkish, preserving the name "app-store-screenshots" only if it appears in the source text. The source text does not contain the name "app-store-screenshots" explicitly; it appears only in the instruction as the name to preserve, but not in the <text> block. So we should not include it in the translation. The text is a description of an agent skill for creating App Store and Google Play screenshots. We need to translate the entire text, including the list of uses and triggers. Keep technical terms like "iOS/Android", "ASO", "App Store", "Google Play", "screenshots", "preview videos", "device mockups", etc. as they are or use common Turkish equivalents if appropriate. For example, "App Store" and "Google Play" are proper names, keep them. "screenshots" can be "ekran görüntüleri". "ASO" is an acronym, keep it. "app store optimization" can be "app store optim

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

halt-catch-fire tarafından daha fazla skill

ai-image-generation
halt-catch-fire
GPT-Image-2, FLUX, Gemini, Grok, Seedream, Reve ve inference.sh CLI üzerinden 50'den fazla model ile AI görselleri oluşturun. Modeller: GPT-Image-2, FLUX Dev LoRA, FLUX.2 Klein LoRA, Gemini 3 Pro Image, Grok Imagine, Seedream 4.5, Reve, ImagineArt. Yetenekler: metinden görsele, görselden görsele, iç boyama, LoRA, görsel düzenleme, yükseltme, metin oluşturma. Kullanım alanları: AI sanatı, ürün maketleri, konsept sanatı, sosyal medya grafikleri, pazarlama görselleri, illüstrasyonlar. Tetikleyiciler: flux, görsel oluşturma, ai görsel, metinden...
creativemediaimage
ai-video-generation
halt-catch-fire
Google Veo, Seedance 2.0, HappyHorse, Wan, Grok ve 40'tan fazla model ile inference.sh CLI üzerinden yapay zeka videoları oluşturun. Modeller: Veo 3.1, Veo 3, Seedance 2.0, HappyHorse 1.0, Wan 2.5, Grok Imagine Video, OmniHuman, Fabric, HunyuanVideo. Yetenekler: metinden videoya, görüntüden videoya, referanstan videoya, video düzenleme, dudak senkronizasyonu, avatar animasyonu, video yükseltme, foley ses. Kullanım alanları: sosyal medya videoları, pazarlama içerikleri, açıklayıcı videolar, ürün tanıtımları, yapay zeka avatarları. Tetikleyiciler: video oluşturma
creativevideomedia
twitter-automation
halt-catch-fire
Twitter/X otomasyonu: inference.sh CLI ile gönderi, etkileşim ve kullanıcı yönetimi. Uygulamalar: x/post-tweet, x/post-create (medya ile), x/post-like, x/post-retweet, x/dm-send, x/user-follow. Yetenekler: tweet gönderme, içerik planlama, gönderi beğenme, retweet yapma, DM gönderme, kullanıcı takip etme, profil alma. Kullanım alanları: sosyal medya otomasyonu, içerik planlama, etkileşim botları, kitle büyütme, X API. Tetikleyiciler: twitter api, x api, tweet otomasyonu, twitter'a gönderi, twitter botu, sosyal medya otomasyonu, x...
marketingapicommunication
ai-avatar-video
halt-catch-fire
We need to translate the given text from English to Turkish. The target language is Türkçe. The directory item type is agent skill, and the name to preserve is "ai-avatar-video". The instruction says: "Translate only the text inside <text>. Do not include the name unless it appears in the source text." The name "ai-avatar-video" does not appear in the source text, so we should not include it. Also, do not include labels like "description", "server name", or "skill name". Just translate the content. The text: "Create AI avatar and talking head videos via inference.sh CLI. Recommended: P-Video-Avatar (fastest, cheapest, built-in TTS). Also: OmniHuman, Fabric, PixVerse. Audio: Inworld TTS-2 (100+ languages, emotion steering for characters), ElevenLabs, Kokoro. Capabilities: audio-driven avatars, text-to-avatar, lipsync videos, talking head generation, virtual presenters, UGC content. Use for: AI
videocreativemedia
agent-browser
halt-catch-fire
AI ajanları için inference.sh üzerinden tarayıcı otomasyonu. Web sayfalarında gezinme, @e referanslarıyla öğelerle etkileşim, ekran görüntüsü alma, video kaydetme. Yetenekler: web kazıma, form doldurma, tıklama, yazma, sürükle-bırak, dosya yükleme, JavaScript çalıştırma. Kullanım alanları: web otomasyonu, veri çıkarma, test, ajan taraması, araştırma. Tetikleyiciler: tarayıcı, web otomasyonu, kazıma, gezinme, tıklama, form doldurma, ekran görüntüsü, web'de gezinme, playwright, başsız tarayıcı, web ajanı, internette gezinme, video kaydetme
browser-automationweb-scrapingtesting
web-search
halt-catch-fire
We need to translate the given text from English to Turkish, preserving specific terms like "web-search", "Tavily", "Exa", "inference.sh CLI", "RAG", etc. The instruction says to preserve product names, protocol names, URLs, numbers, and technical terms. So "Tavily", "Exa", "inference.sh CLI", "RAG", "AI", "API" should remain as is. Also "web-search" is the name to preserve but it's not in the text? Actually the name is "web-search" but the text doesn't contain that exact string. The text has "web search" (two words). The instruction says "Do not include the name unless it appears in the source text." So we translate "web search" as "web araması" or similar? But careful: "web search" appears multiple times. We should translate it as "web araması" but keep technical terms like "Tavily Search" as is? The instruction says preserve product names. "Tavily Search
researchweb-scrapingapi
infsh-cli
halt-catch-fire
inference.sh CLI üzerinden 250'den fazla AI uygulamasını çalıştırın - görüntü oluşturma, video oluşturma, LLM'ler, arama, 3D, Twitter otomasyonu. Modeller: FLUX, Veo, Gemini, Grok, Claude, Seedance, OmniHuman, Tavily, Exa, OpenRouter ve daha fazlası. AI uygulamalarını çalıştırırken, görüntü/video oluştururken, LLM'leri çağırırken, web araması yaparken veya Twitter'ı otomatikleştirirken kullanın. Tetikleyiciler: inference.sh, infsh, ai model, run ai, serverless ai, ai api, flux, veo, claude api, image generation, video generation, openrouter, tavily, exa search, twitter api, grok
developmentapicreative
landing-page-design
halt-catch-fire
Açılış sayfası dönüşüm optimizasyonu; düzen kuralları, kahraman bölümü tasarımı ve CTA psikolojisi ile. Ekran üstü formülü, sosyal kanıt yerleşimi, mobil tasarım ve F-deseni okumayı kapsar. Kullanım alanları: startup açılış sayfaları, ürün sayfaları, SaaS pazarlama, dönüşüm optimizasyonu. Tetikleyiciler: açılış sayfası, kahraman bölümü, ekran üstü, dönüşüm optimizasyonu, açılış sayfası tasarımı, cta butonu, kahraman görseli, açılış sayfası düzeni, saas açılış sayfası, ürün sayfası tasarımı, dönüşüm oranı