Who this is for: App founders and marketers introducing a new mobile product.
What to prepare
- Approved portrait screens from a consistent app version
- One verified task and its actual completion state
- Approved app identity and exact copy
- Current availability and destination
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Illustrative brief: introduce a fictional field-note app through capturing one observation and finding it again. Begin with the need to record a detail, show the supplied note-entry screen, reveal the example note and hold its verified saved state. Return to the list so the same note is identifiable. Use close portrait crops with a stable title or navigation anchor. Keep essential meaning visible without narration. Do not imply automatic location capture, offline support, synchronization or a store release unless those facts are supplied. End with the app's actual availability and one supported next action. The example is a planning scenario, not a rendered video or customer result.
Choose the right app moment
The strongest starting point is a task with a clear beginning and result: capture a note, select a slot or inspect a record. A task helps a new viewer understand what the app is for before they need to learn its navigation.
This job is suitable for an app whose important behavior can be represented with approved screens or verified footage. A complex setup process may need a separate walkthrough rather than being hidden behind a polished launch reveal.
Prepare suitable inputs
Use matching portrait assets with consistent sample data, theme and device context. Identify the exact label that confirms the result. A pending request and a completed booking are different outcomes, even if both screens contain a checkmark.
Unsuitable inputs include unrelated screens from different versions, private user data, mockups presented as released UI and a feature list without a demonstrable task. A concept can still support a teaser if its status is explicit.
- Useful source packet: start state, meaningful action state, final state and approved availability copy.
- Planning decision: choose whether each scene needs a full device view or a readable close crop.
- Scope boundary: a general launch film does not automatically satisfy a store's preview requirements.
Build and check the launch
Start with the task and identify the evidence needed to show it. Arrange the portrait scenes so one object persists through the action. Approve the meaning before adding decorative transitions or device effects.
Review the storyboard for unsupported gestures and implied capabilities. Then inspect the real final artifact at the intended presentation size, checking the saved state, crop boundaries and closing copy.
If the source assets cannot prove the desired result, narrow the claim or obtain the missing state. Do not invent a finished screen to complete the story. The illustrative brief above is a production starting point; it still requires actual approved assets and a current access statement.
Review checklist
- The app is introduced through one recognizable task.
- Portrait assets preserve consistent state and example data.
- The final label describes the actual outcome.
- Device imagery does not add unsupported capabilities.
- Availability is verified.