Store‑Ready Creative from a Clickable Demo: A 5‑Asset Export Workflow for ASO & Paid Ads

A short playable demo forces you to pick the core user journey and the real interactions people will experience. App Store previews and screenshots that show real, contextual flows convert better and avoid reviewer friction because they reflect the in‑app experience rather than conceptual mockups.

Using the prototype as the single source of truth reduces rework: capture frames, record live interactions, and extract copy directly from the UI. This keeps product, design, and marketers aligned and speeds up iterations when you test different messaging variants in ASO or ad campaigns.

1) ASO screenshots (primary install drivers): hero screenshot + 3 supporting frames that show top tasks. Apple requires specific sizes (6.9" iPhone mandatory for iOS) and accepts scaled uploads from other sizes if missing; Google Play has its own size and content rules. Follow store specs to avoid scaling artifacts or reviewer rejections.

2) App Preview storyboard and poster frames: App Previews must show the real in‑app experience and are limited to 15–30 seconds per preview on Apple. Build a short storyboard of scenes (3–6 cuts) that map to the playable’s strongest moments — opening, core action, outcome — and plan silent‑first visuals because previews autoplay muted.

Set up one prototype file as the canonical export workspace. For each scene create dedicated export frames named with this pattern: <assetType>_<locale>_<deviceClass>_<sequence>. Example: screenshot_en-US_iPhone6.9_01. Use components for device shells and text overlays so you can swap localization without altering the base frame.

Export settings: PNGs for screenshots (lossless) at the exact pixel sizes required by App Store Connect; use HEIF/PNG depending on platform guidance if you prefer smaller files but check current store acceptance. For preview video poster frames export as PNG at the native preview dimensions and use a .mov or .mp4 for uploads per each store’s accepted format.

Content restrictions: both stores prohibit misleading claims, pricing language, and references to other platforms in creative. For App Previews Apple enforces that the video demonstrates the actual in‑app experience. Avoid using real user data or private info in screenshots — use sanitized/demo content to reduce privacy flags during review.

Text sizing and contrast: design overlay text to meet readable contrast and safe area rules. On small screens keep critical text above the system UI and avoid placing CTA elements inside rounded corners or notch zones. When localizing, allow for 20–40% longer strings and check visual wraps in each exported language.

Deliver a single zipped handoff with: (A) exported PNG poster frames and full‑size screenshots for each device class and locale, (B) a 3‑6 step storyboard document (PNG + one‑line intent per cut), (C) raw 15–30s editable video timeline (or reference footage + frame timestamps), (D) three ad frame variants (static 1:1, 4:5, 9:16) and (E) store copy file (title, subtitle, short and long descriptions) with localization keys.

Include a short runbook in the zip: exact upload filenames for App Store Connect and Play Console, required metadata (locale, device class), orientation (portrait/landscape), and a QA checklist: visual consistency, safe‑area check, localized copy length check, and a final compliance run against store submission rules.