Who this is for: App founders and marketers preparing a mobile launch story.
What to prepare
- A representative mobile task
- Matching approved portrait screens
- A product name, availability statement and next action
Select a moment that benefits from the app
For an illustrative field-note app, the task is capturing an observation and finding it later. The product may also have folders, themes, sharing and account settings, but those features do not all belong in the first launch sequence.
Write the task as a beginning and an end: the user starts with an observation to record and finishes with a saved note they can identify. Include the minimum states needed to understand the transition. Do not imply location capture, offline operation or device access unless those behaviors are verified.
Work through a portrait-screen scene plan
The following outline is a planning exercise using fictional content. It can be adapted to a 30-second brief, with final timing determined by the supplied copy and screens.
- Opening: show the need to record “Cracked sign beside the north gate,” explicitly as example content.
- Orientation: show the app's note-entry screen with the relevant field readable.
- Action: enter or reveal the supplied note. Keep the field label visible so the viewer understands the input.
- Confirmation: show the saved note and its actual supplied status, not a decorative checkmark invented for the film.
- Retrieval: return to the list and identify the same note.
- Close: show the product identity and verified availability, with one next action.
Choose crops around information, not the device frame
A phone mockup can provide context, but a large decorative device border may leave too little space for the interface. Decide which scenes need the full device and which need a closer view. Keep a stable label or object during the transition so the viewer knows where the crop came from.
Do not animate a fingertip or cursor in a way that suggests a gesture absent from the supplied workflow. If the source is a still image, use a camera move or annotation to explain it rather than inventing a tap result.
Review the smallest intended presentation of the film. Inspect the saved note, action label and closing status. If they compete, simplify the scene. Moving the phone faster does not solve unreadable UI. The launch can point to a longer walkthrough when setup or exceptions require more space.
Review checklist
- The story follows one note or object from start to finish.
- Screens preserve consistent device, theme and example data.
- Close crops retain enough orientation to identify the task.
- Availability copy does not imply an unverified store release.