AppWispr

Find what to build

Preview‑Video Playbook for Founders: Contractor‑Ready Kit to Produce 15–30s App Previews That Convert

AW

Written by AppWispr editorial

Return to blog
L
AP
AW

PREVIEW‑VIDEO PLAYBOOK FOR FOUNDERS: CONTRACTOR‑READY KIT TO PRODUCE 15–30S APP PREVIEWS THAT CONVERT

LaunchMay 22, 20266 min read1,173 words

AppWispr’s Preview‑Video Playbook gives founders and product leads a ready-to-send contractor brief and a lean production plan to ship store‑compliant 15–30s app previews. This guide focuses on what to direct (storyboards, frame‑accurate shot lists, and three template scripts), what to export (Apple and Google specs), and how to A/B test to prove whether a video actually lifts installs and retention.

preview-video-playbook-15-30s-contractors-kitapp preview videoApp Store video specsGoogle Play videoASOvideo A/B testlocalization

Section 1

Why a 15–30s App Preview is a high‑leverage asset

Link section

App previews occupy prime real estate on both the App Store and Google Play and autoplay for many users — that makes them one of the highest-leverage assets for converting store visitors into installs. But they’re also technical: Apple requires previews to be 15–30 seconds and strict about device dimensions and encoding, and Google Play shows previews before screenshots and may autoplay muted clips up to 30 seconds. Start with the platform requirements before any creative work to avoid wasted production time.

Treat the preview as a conversion experiment, not a demo dump. Use the first 3–7 seconds to communicate a single clear value proposition (the hook) and then demonstrate one high‑impact task in real UI. Keep overlays short and legible: long paragraphs or multiple feature lists kill attention.

  • App Store: previews must be 15–30 seconds and follow Apple’s encoding and device‑size rules.
  • Google Play: previews appear before screenshots, can autoplay muted up to ~30s, and should be concise.
  • Hook in first 3–7 seconds; show one core task with real UI interactions.

Section 2

Contractor brief: storyboards, three template scripts, and frame‑accurate shot lists

Link section

Write a one‑page creative brief for contractors that includes: the single conversion goal (e.g., trial starts), primary persona, device orientation(s), and the store language/locale. Attach the storyboard: a 4–6 frame strip that maps seconds to visual and text overlay. For example: 0–3s (hook headline + action), 4–12s (core flow), 13–22s (benefit + social proof or CTA), 23–30s (app logo + CTA).

Use three short, tested script templates you can swap by hypothesis: (A) Product Hook — fast UI + headline showing what it does; (B) Benefit Story — short user‑context scene then product solves it; (C) Walkthrough — stepwise task completion with microcopy overlays. Each script should map to a frame‑accurate shot list that specifies exact timestamps, frame in/out, UI element shown, tap/cursor motion, and overlay text.

  • Deliverables for contractor: storyboard PDF, 3 script options, device‑specific shot lists (timecode + action), poster frame, and required export presets.
  • Shot list example line: 00:04–00:08 — Inbox screen, tap Compose (finger), show compose modal, overlay: “Send quick follow‑ups”.
  • Limit scripts to 35–45 words for 15s and 60–75 words for 30s to maintain readable on‑screen text.

Section 3

Localization shortcuts and production efficiency hacks

Link section

Localize smart, not exhaustively. Translate only critical overlays (hook headline, CTA, and short labels) and leave UI text visible where it’s already localized in the app. For many language variants you can reuse the same video master and swap a localized text layer in post or use subtitle files — this is faster than full re‑recording.

For contractors, request projects delivered as an edit + compositing file (Premiere/Final Cut/After Effects) plus a flattened master per resolution. That lets you swap localized overlays, change poster frames, and re‑export without a full re‑shoot.

  • Localize overlays and CTAs first; defer full UI re‑captures unless UI text is unlocalized.
  • Ask for editable project files and separate subtitle/caption files for quick language swaps.
  • Provide contractors with a localization spreadsheet keyed to timecodes (e.g., 00:03–00:07 Hook headline) to speed swaps.

Section 4

Export specs that pass Apple and Google the first time

Link section

Follow platform docs exactly. Apple’s official App Preview spec lists the 15–30s duration requirement and device‑specific dimensions (portrait and landscape variants) and enforces strict encoding. Google Play’s help center explains that preview videos display before screenshots and can autoplay muted for up to 30 seconds; Play often prefers a YouTube link for video hosting. Use H.264 (AVC) with AAC audio and match the exact frame rate and pixel dimensions for the target device to avoid rejections.

Common production checklist for final masters: exact resolution for each device size, constant 30fps (or the platform’s specified fps), H.264 codec with baseline or main profile, stereo AAC (even if silent), correct duration (15–30s), and a high‑quality poster frame (first frame is often used). If you produce multiple orientations, export a separate master per orientation and language as required by App Store Connect or Play Console.

  • Apple: 15–30s; export per device dimension listed in App Store Connect. Use H.264/AAC and check poster frame rules.
  • Google Play: upload a hosted (YouTube) or file preview; ensure mute/autoplay experience and clip <=30s.
  • Always include a stereo AAC track (some platforms reject silent files without an audio track).

Section 5

A/B test plan: measure impact on installs and retention

Link section

Run an A/B test before you assume a video helps. Use a store‑listing A/B testing platform or Play Store experiments (where available) to compare: control (screenshots only) vs variant (screenshots + video). Define success metrics in advance: install conversion rate (visitors → installs) as primary, and short‑term retention (day‑1 and day‑7) as secondary to detect unhelpful promises that drive churn.

Design experiments to test one variable at a time: Hook vs Benefit script, 15s vs 30s, localized overlay vs English overlay. Collect at least a few thousand visitors per variant if possible; if traffic is small, run sequential short experiments and use consistent measurement windows. Track downstream metrics in your analytics (trial starts, activation events) to see if the preview attracts quality users or only curiosity installs.

  • Primary metric: conversion rate (store view → install). Secondary: D1/D7 retention, activation events.
  • One variable per test: e.g., same screenshots + two video scripts.
  • If store traffic is low, prioritize rapid sequential tests and cohort‑level retention checks.

FAQ

Common follow-up questions

How long should my preview be — 15 or 30 seconds?

Both are allowed; choose 15s when you need a fast hook (single benefit) and 30s when you must demonstrate a short flow. The priority is clarity in the first 3–7 seconds. Apple requires between 15 and 30 seconds, and Google Play supports up to 30s.

Do I need separate videos per device orientation and language?

Apple requires device‑sized previews for specific devices; deliver per relevant device size and orientation for your target audience. For languages, prefer swapping localized overlays on an editable master to avoid full recaptures unless UI text is unlocalized.

What technical spec causes the most App Store rejections?

Common failure points are wrong resolution/frame rate, missing or incorrect audio track, and overlay content that violates review rules. Follow Apple’s App Preview specifications exactly and submit a poster frame that conforms to their guidance.

How do I know if the video improved acquisition quality?

Measure install conversion rate for the variant and track D1/D7 retention and core activation events. A video that raises installs but lowers retention indicates a mismatch between promise and product; the test should reveal that.

Sources

Research used in this article

Each generated article keeps its own linked source list so the underlying reporting is visible and easy to verify.

Next step

Turn the idea into a build-ready plan.

AppWispr takes the research and packages it into a product brief, mockups, screenshots, and launch copy you can use right away.