Who this is for: Product teams preparing a timed storyboard for an original launch asset.
What to prepare
- Approved portrait screens
- One consistent fictional example object
- Exact confirmation wording
- Verified app identity and availability
Scene-by-scene storyboard
30-second planning sequence · illustrative copy and visual direction
- 01
0–4s
Recognize the need
Show an illustrative observation card beside a stable phone frame.
On screen:Capture the detail before moving on.
- 02
4–9s
Orient the input
Show the supplied note-entry screen with its title and input region readable.
On screen:Add the observation.
- 03
9–16s
Create the note
Reveal the example text, 'Cracked sign beside the north gate,' using approved states rather than invented input behavior.
On screen:One note, with the relevant detail.
- 04
16–23s
Verify the save
Hold the actual supplied saved-state confirmation and preserve the note title.
On screen:Check that the note is saved.
- 05
23–27s
Find it again
Return to the supplied list and identify the same note.
On screen:Find the same note in the list.
- 06
27–30s
Close with availability
Display approved identity and current access wording.
On screen:See current availability.
Make it your own
- Example task
- Choose one supported mobile action.
- Confirmation
- Use the actual saved, sent or pending state.
- Availability
- Do not imply an unverified store release.
Define the success
The example is a fictional note-capture scenario. Its result is a saved, findable note, not automatic location capture, offline operation or a productivity improvement.
Use actual supported behavior when replacing the example. If the product saves only a draft or requires another step, the storyboard must show that state accurately.
Adapt the portrait composition
Use close views for the input and result while preserving the note title as an anchor. A full phone frame is useful for orientation but should not make the important text unreadable.
A 15-second cut can omit the initial observation card and shorten the identity scene. A 60-second version can explain a meaningful prerequisite or retrieval step.
Prepare and check the assets
Supply matching screens from the same version, theme and example account. Review the entire image for private or unrelated information before production.
This is a general mobile launch storyboard. Store-specific preview requirements are a separate delivery check and may require different footage or structure.
Review checklist
- One example object remains continuous.
- Portrait crops preserve orientation.
- The final state uses exact verified wording.
- Device imagery adds no unsupported capability.