The template
Plan a device-focused preview around real app footage and a short, clear feature story.
Use this scene sequence as an editable outline. Replace sample wording with verified details; the sequence is a planning aid, not a fixed duration or a platform specification.
| Beat | On screen | Narration | Review check |
|---|---|---|---|
| 1. Recognize the app | Show the actual home screen on the target device. | Name the task the app helps complete. | Is this the submitted app version? |
| 2. Start the feature | Open the selected feature from its real entry point. | Explain why this feature matters to a new user. | Does the route match current navigation? |
| 3. Use it | Show one meaningful action and response. | Describe what the viewer can do next. | Is the capability generally available? |
| 4. Reveal the result | Hold on the finished app state. | Keep the benefit specific and supportable. | Can a viewer read the screen at phone size? |
| 5. Close | End on the app and any permitted end frame. | Use only a next step allowed by store rules. | Recheck current Apple preview requirements. |
How to fill it in
- Hook: state the viewer's problem or the outcome they want.
- Context: show only the setup the viewer needs to understand the workflow.
- Main action: focus on one or two meaningful product steps.
- Outcome: show what changed, using only claims you can support.
- Next step: give viewers one specific action to take.
Customize it for your audience
Adapt this outline to the store audience and the specific device shown. A first-time user may need the entry point and a visible result; an existing user may benefit more from a recently added workflow. Capture the real interface at the intended orientation and avoid staging screens that cannot be reached in the submitted build. If multiple features need explanation, make separate previews with a single promise each. Before delivery, compare each frame with the store listing copy and verify that claims, overlays, audio and end frames follow the current store rules for the target locale.
Prepare the final handoff
Prepare the preview at the target device size and keep a record of the app version, language and store listing it represents. Review the opening frames as a viewer would encounter them in the listing, then inspect the full clip with sound off and on. Hand off the source capture, approved copy and destination-specific export together so a later interface update can be matched to the right preview.
Production and approval checklist
Before recording or animation, confirm the viewer, destination, desired next action and product version. Replace every illustrative name, number and screen with approved material, or label it as sample content. Check that each scene advances the story and that voiceover fits the time available on screen. Review the draft once for product accuracy, once for audience comprehension and once for permissions, accessibility and destination requirements. Make the final reviewer and approval date explicit; recheck volatile facts such as pricing, availability, release status, event details and platform rules just before publishing. Keep the script, source assets and approved export together so an update can be made without guessing which version is current.
Who it serves
People comparing apps need to recognize the task and see the interface behave. Lead with one feature that matters to the listing audience, and let the real app screens carry the explanation.
Evidence and review
Check the target device, orientation, current feature availability and Apple's current preview rules. This outline does not validate codec, frame rate, audio or submission acceptance.
Avoid overlays, device frames or calls to action until you have checked the current App Store preview rules. A marketing clip and a store preview can have different content constraints.
A worked example
Illustrative scenario, not a customer story: Open on the app's main screen, show one permitted feature in use, then close on the result. Check the current store rules for device frames, length and overlays before submission.
Make it automatically
DemoVexa can use your product code and project context to draft a brief, script, and scene plan. Review every screen, claim, permission, and recording before publishing.
Frequently asked questions
Should an App Store preview cover the whole app?
No. Choose one connected feature story. A quick sequence that starts in context, shows the feature and ends on its result is easier to understand than a rushed list of unrelated screens.
Does this checker guarantee Apple will accept the video?
No. This page is a planning template, not a validation service or Apple approval. Verify current device-specific resolution, length, format, audio and content requirements in App Store Connect before submission.
Can I use this template for free?
Yes. The outline is page content you can copy without an account. Adapt it to your product, check the destination's current requirements, and verify every claim, date, permission and third-party asset before publication.
Make your next product video with DemoVexa
Download the app to make a video from your code, or start a free trial with 15 renders.