App Preview video: specs, content, and review perception
Preview dimensions, duration, showing real UI, and avoiding misleading edits. Consistency with screenshots matters more than polish. Telegram @hagee66.
This guide · Guide library · Apple listing · Google listing · Both stores · Telegram @hagee66
App Preview on the store page is often over-hyped as “a film” and under-valued as “auto-rotating screenshots.” Its job is simple: in ten seconds prove the main path promised in screenshots and description is real—users see taps, UI response, and outcomes. Over-cut reels, interactions not in the build, or marketing footage posing as in-app capture hurt review perception and “not as advertised” reviews.
Goee (goee.cc) covers specs, content, editing ethics, and platform differences. Resolution caps, duration, format, and whether video is mandatory follow official pages. Polish never replaces crash precheck or build fidelity; video does not promise easier approval.
What this guide solves
Common rework on preview video:
- After Effects “concept UI” not in the submitted build.
- Video skips login; description says “sync with account.”
- Same animation looped to fill time—reviewers and users cannot see core value.
- Preview and first screenshot tell different stories above the fold.
- Undeclared capabilities in video (e.g. background location trails) vs privacy label.
- One landscape clip for both platforms, cropped unreadable on portrait pages.
If you are syncing screenshot specs and metadata checklist, lock screenshot narrative first, then cut video—not the reverse.
Who should read
- Design and growth: storyboard, capture, export; know forbidden shots.
- Product: one demonstrable path—not a full product trailer.
- Engineering: stable build, test account, no debug overlay.
- Listing: all device sizes exported, file size, backend acceptance.
Custom product pages may need shorter CPP-specific previews—same rules as default page.
Core practice
Specs and device coverage
Apple and Google differ; requirements change. Official docs rule. Prepare:
| Item | Note |
|---|---|
| Source capture | Real device preferred; emulator risky (fonts, performance) |
| Resolution | Export each required size—do not scale one file brutally |
| Duration | Shorter is better—shortest path to one completed task |
| Audio | Previews often autoplay muted—do not rely on voiceover alone |
| On-screen text | Readable; match ASO language |
Check on smallest target device: progress bars, tab labels readable?
Content: one verifiable path
Suggested structure (tweak per category):
- 0–2s: pain in product UI (not actor skits unless video IS the product).
- 2–8s: main path—tap what, enter what, where result appears.
- 8–12s: hold on result—do not cut to five more features.
If subscription/trial/paywall is on the main path, show in-app real pricing aligned with IAP notes—no “tap for lifetime free” captions.
Truth: build, screenshots, description triangle
Reviewers and users cross-check:
- Tab names and buttons match submitted build?
- UGC, gambling, medical claims in video vs age rating answers?
- Region-only features in video but not in description?
Never ship “next version” UI in current submit assets. Video-only rejections: metadata reject fix.
Editing pitfalls
- Do not speed up until taps are unreadable.
- No other apps in comparison edits.
- No unreproducible 3D bumper eating half the runtime.
- Remove watermarks, debug menu, TestFlight orange dot, internal IPs.
- Fake sample data for PII—never real user lists.
Screenshots and CPP
Default page: first screenshot and video open should tell the same story.
CPP previews can be shorter/channel-specific but same boundaries—custom product pages. Do not borrow default video with unreleased features for CPP.
Android note
Play promo video often via YouTube, rules differ from auto-preview—official pages. Maintain a “external video inventory” so iOS review footage capabilities are not missing from Play long description.
Copy-paste templates
Preview storyboard
Product / version:
Build:
Path (one step per line):
1. Open app → see ___
2. Tap ___ → enter ___
3. Result ___ (hold 2s)
Exclude: unreleased pages / competitors / inflated pricing
Capture account:
Device model:
Export sizes:
Matches screenshot 1 line:
Reviewer:
Pre-submit video self-check
□ Every shot reproducible in submitted build
□ No debug / watermark / internal URL
□ Subscription price matches in-app
□ No black bumper in first 3s
□ Understandable on mute
□ No critical crop per size
□ No conflict with first description lines
Common mistakes
| Mistake | Outcome | Fix |
|---|---|---|
| Motion graphics as device | Metadata mismatch | Capture submitted build only |
| Long brand film | High skip rate | Finish within ~12s |
| Voiceover required | Mute fails | Short on-screen text |
| Split from screenshots | Conversion drop | Unified story |
| Undeclared permission demo | Privacy risk | Align privacy labels |
| One clip both stores | Bad crop | Export per platform |
| Rejection—description only | Re-reject | Fix triangle together |
Workflow: capture to listing
Cross-functional pipeline: product freezes path (T-5) → eng build without overlay (T-4) → design capture and rough cut (T-3) → listing exports sizes (T-2) → product+legal scan claims/pricing (T-1) → upload with screenshots in Connect.
Capture day: disable low-battery prompts, developer menu; fixed test account (like review test account, no password on screen). Stable Wi‑Fi; if showing weak network, in-app copy must say “requires network”—do not hide error toasts.
Keep project file + caption-free master three months. Replace one frame without full reshoot. Multi-market: one language UI in video—either re-capture other locales or do not attach video there.
iPad + iPhone: separate slots—same story, two crops; hit targets readable in both aspect ratios.
Policy perception: reproducible promise, not art license
Reviewers ask: can I reproduce this after install? Flashy transitions lose to half-second on result screen. Health, fintech, education: avoid before/after cure or return claims; kids—no sudden external links or unrated social. See age rating and content.
FAQ
No budget—skip video?
Many categories succeed on screenshots alone. Video is optional, not a review requirement; if you cannot keep it truthful, omit.
UGC in preview?
Portrait rights, content/rating alignment; risky UGC out of official preview.
English video, Chinese description?
Match locale per market; mixed language hurts ASO and trust.
Update cadence?
Resync on major path change; not every bugfix—see product page optimization.
Agency can cut?
Spec and consistency check—creative and rights stay client. Telegram @hagee66 with storyboard and build ready.
Next steps
Back to guide library · Specs and policy per official pages. Goee does not promise approval.