Write the question at each destination
Someone on a store listing may be evaluating an install. A social viewer may not yet recognize the problem. A landing-page visitor may need evidence for one feature claim. Treat these as audience hypotheses to check, not guaranteed behavior.
Write the question for each placement. This explains why the same opening, ending and footage might not suit every location, even when all versions describe the same truthful task.
Check current official requirements
Apple’s app-preview guidance emphasizes demonstrating the app experience using device-captured footage. Its specifications and submission guidance govern the file you prepare. Google Play provides separate preview-asset and video guidance.
Read the linked official pages for the destination, device and locale. A remembered export size is not a compliance check. This guide neither certifies acceptance nor uploads a store video on your behalf.
| Decision or state | Example | Review |
|---|---|---|
| Apple preview | Show the app experience | Use current Apple capture/content/file guidance. |
| Google Play video | Explain the app’s use | Check current preview-asset setup. |
| Social promo | Introduce a relevant task | Review placement and truthful next step. |
| Landing demo | Support the page’s claim | Verify claim-to-screen match. |
Share source recordings, not assumptions
For a fictional timer app, capture the real action of grouping work sessions and the resulting grouped view. Keep that source apart from destination exports. Reuse it only where permissions and destination rules allow.
A social version might introduce the viewer’s problem. A store version needs its own review as an app experience. A landing version could focus on the grouped result. None should add behavior the source cannot establish.
Version exports and recheck at upload
Label each export by placement and obtain separate approval. Check opening, overlays, narration, device presentation, rights and ending. When requirements conflict, make separate assets or hold the destination rather than dropping a necessary qualification.
Save capture date, build, guidance links and export revision together. Revisit them after an interface change. After publication, inspect the real listing or page: a successful local export only proves that a file exists.
Copy the planning worksheet
Use this worksheet in your own notes. Fill it with verified product details and actual review observations before sharing an asset.
Destination / locale:
Viewer question:
Source filename and app build:
Specific opening / ending:
Official guidance and review date:
Rights / qualifications:
Approved revision:
Hosted check:Official references
Requirements and reporting can change. Check the current source for your destination before relying on a specification.
Browse the founder guide library for the next task in your workflow.