Launch Without Reworks: Exact Asset‑Handoff Checklist for Icons, Screenshots & Preview Videos

Always produce a single, layered master file per asset type (icons: 1024×1024 PNG/PDF source; screenshots: layered artboard with editable text; videos: source project with separate tracks). That master is the only file your contractors should edit — everything else is exported from it with automated presets.

Create and share explicit export presets for every required store size and device class. For iOS icons and screenshots, export a 1024×1024 master icon and the App Store / device display sizes Apple requires; for Android include Play Console sizes and the adaptive icon layers. Providing these presets eliminates guessing and reduces resizing artifacts.

Use deterministic, human‑and‑script readable names so engineers, store managers, and automation tools can find files without asking. A recommended pattern: {product}-{assetType}-{deviceOrLocale}-{role}-{v#}.{ext}. Example: myapp-icon-appstore-1024x1024-v1.png or myapp-ss-6.9inch-en-US-feature1-v2.jpg.

Version every exported file and keep a single canonical manifest (CSV/JSON) listing filenames, resolution, color profile, and whether the file is approved for upload. This manifest becomes the source of truth for build pipelines and localizers and prevents accidental uploads of work‑in‑progress files.

Treat screenshots as templates with replaceable text layers rather than separate images per locale. Deliver a master template plus exported variants for each store‑locale pair. That means: one source artboard, and N exports (en‑US, fr‑FR, ja‑JP, etc.) named consistently.

Include localization notes in the manifest: character limits, recommended line breaks, and alternative UI crops (some languages require longer text). Provide translators a screenshot context file showing which UI strings map to which screenshot areas to avoid mistranslations and layout overflow that cause rework.

Create a time‑stamped storyboard that maps story beats to device frames (which screenshot or microinteraction is on screen at 0:04, 0:08, etc.). For App Store previews Apple requires 15–30 seconds and exact device resolutions; frame rate and audio channel expectations matter — include them in the deliverable. A compact storyboard prevents unnecessary reshoots and keeps editors aligned with product priorities.

Provide an export checklist: target resolution(s) for preview device classes, 30 fps (if required by the store), codec/container (H.264/MP4 or Apple‑specified), stereo track present (even if silent), length limits, and a file size guidance. Include QA steps that a reviewer can run locally (open on device simulator, check for UI cropping and legibility) to catch issues before upload.

Before handing assets to the release manager run a short, reproducible QA checklist. Key checks: filename matches manifest; correct color profile (sRGB for stores); no alpha channel where the store disallows it; texts are localized and don’t overflow; icon has required padding and no store‑banned content (e.g., device frames or UI screenshots where disallowed).

Add an upload simulation step: test the asset in a staging/preview view (App Store Connect or Play Console preview, or a local mock) to confirm visual acceptance. Keep one team member responsible for cross‑checking the manifest against what the store expects; this single point of ownership avoids fragmented approvals that lead to rework.