# Screenshots for store listing are provided and representative

- **Pattern:** `ab-001937` (`mobile-store-readiness.visual-assets.screenshots-provided`)
- **Severity:** medium
- **Lifecycle:** active
- **Last modified:** 2026-04-18
- **Canonical URL:** https://auditbuffet.com/patterns/ab-001937
- **License:** CC-BY-4.0 — attribute to AuditBuffet Pattern Catalog (https://auditbuffet.com/patterns/ab-001937)

## Why it matters

Store screenshots are the primary conversion surface for most app listings — industry data consistently shows screenshots determine whether a user installs after landing on the listing page. Apple App Store requires at least one screenshot per supported device class; Google Play requires a minimum of two. Providing only one, or providing low-resolution screenshots (under 1080px wide), causes store listing rejection and leaves the listing with no visual evidence of what the app does. For context: Apple's screenshot spec (apple-app-store-screenshots) requires 1170×2532 for iPhone 14/15 class devices; submitting a 480×854 screenshot will be rejected outright.

## Severity rationale

Medium because missing or undersized screenshots cause store listing rejection and eliminate the primary visual conversion driver for new installs.

## Remediation

Capture at least two screenshots showing distinct app screens (home, core feature, user benefit). Export at the platform minimums and organize by platform.

```
screenshots/
  ios/
    01-home.png        # 1170x2532 (iPhone 14 class)
    02-feature.png
  android/
    01-home.png        # 1080x1920 minimum
    02-feature.png
```

Use Figma, Adobe Express, or ScreenFlow to add feature callout text (optional but improves conversion). Export as PNG or JPEG. For iPad listings, also provide 2048×2732 screenshots — App Store treats iPad and iPhone as separate submission artifacts.

## Detection

- **ID:** `screenshots-provided`
- **Severity:** `medium`
- **What to look for:** Look for screenshot assets in a screenshots/ directory or metadata files that reference store listing screenshots. Check if there are 2-5 high-quality screenshots that show key app features. Verify screenshots are correctly sized for store guidelines (iOS App Store: 1170x2532 for iPhone, 2048x2732 for iPad; Google Play: 1080x1920 minimum).
- **Pass criteria:** Count all screenshot files found in the project. At least 2 and no more than 10 screenshots exist that show different features/screens of the app. Screenshots are at minimum 1080 pixels wide for stores. Report even on pass: "Found X screenshots in Y directories."
- **Fail criteria:** No screenshots found, only 1 screenshot provided, or screenshots are very low resolution (under 800 pixels in height).
- **Skip (N/A) when:** Project is in pre-release phase and screenshots have not been created yet (acceptable for internal testing).
- **Detail on fail:** `"Only 1 screenshot found — stores typically require 2-5 to show app features"` or `"Screenshots are 480x854 — below recommended 1080x1920 for Google Play"`
- **Remediation:** Store listings use screenshots to show potential users what your app does. Create 2-5 screenshots:
  1. Take screenshots of key screens (home, main features, user benefits)
  2. Add overlays or text explaining each feature (optional but recommended)
  3. Resize to store requirements:
     - iOS: 1170x2532 (portrait) or 2388x1668 (landscape)
     - Android: minimum 1080x1920 (portrait) or 1920x1080 (landscape)
  4. Organize in a `screenshots/` directory:
     ```
     screenshots/
       ios/screenshot-1.png
       ios/screenshot-2.png
       android/screenshot-1.png
       android/screenshot-2.png
     ```
  4. Use free tools like Figma, Adobe Express, or ScreenFlow to capture and annotate
  5. Save screenshots as JPG or PNG, organized by platform

## External references

- external apple-app-store-screenshots — https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications
- external google-play-store-listing — https://support.google.com/googleplay/android-developer/answer/9866151

Taxons: findability, regulatory-conformance

HTML version: https://auditbuffet.com/patterns/ab-001937