Who this is for: Launch teams translating a specific creative job into a motion brief.
What to prepare
- Matching portrait screens for one task
- Exact controls and confirmation wording
- Approved app identity
- Verified availability
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Create a 30-second mobile app launch concept for PRODUCT_NAME. Follow ONE_TASK from START_STATE to VERIFIED_RESULT using only the supplied portrait screens. Keep EXAMPLE_OBJECT recognizable throughout. Do not add gestures, permissions, synchronization or device features that the source material does not establish. Open with a short description of the user's need. Show enough of the phone interface to orient the viewer, then move closer to the relevant action. Preserve a stable title or navigation anchor during each crop change. Use the supplied intermediate state to explain the action and hold the actual confirmation long enough to inspect its wording. Treat the device frame as supporting context rather than the main subject. Keep on-screen explanation outside important controls. Return to the saved or completed object so the result is concrete. Close with CURRENT_AVAILABILITY and NEXT_ACTION. Do not imply an app-store release unless the supplied status confirms it. All fictional sample data should remain identified as illustrative.
Make it your own
- ONE_TASK
- Choose an action with a clear beginning and completion.
- EXAMPLE_OBJECT
- Keep the same note, booking or item across screens.
- VERIFIED_RESULT
- Use the exact supplied confirmation, including any pending state.
- PRODUCT_NAME and START_STATE
- Supply approved app identity and the exact initial screen, role and setup for the one task.
- CURRENT_AVAILABILITY and NEXT_ACTION
- Use the verified release state and destination without implying an unconfirmed app-store listing.
Choose a meaningful first success
An illustrative note app might begin with an observation, save it and show the same note in the list. The useful result is a saved, findable note. A decorative checkmark alone does not establish that.
If the task needs setup, include a concise prerequisite or choose an example that begins in a configured account.
Adapt the device framing
For a small presentation, crop tightly enough to read the action while retaining a title. For a wider composition, put the task explanation alongside the portrait screen.
For a longer version, add the retrieval step rather than repeating the save animation. This shows what the viewer can inspect next.
Correct a false success implication
If the source says “Request submitted,” do not label it “Booking confirmed.” If the screenshot sequence lacks a resulting state, request the asset or frame the scene as a concept.
A generic app launch film and a store-specific preview are different production jobs. This prompt supplies a creative launch brief, not platform approval.
Review checklist
- The same object persists across portrait screens.
- Confirmation wording matches the source.
- Crops preserve orientation and important controls.
- Availability is verified rather than inferred.