App demo brief
An app demo works best when it follows one task from the starting state to the result. Use this brief to specify which screens matter and what the viewer should understand.
Choose the task before the feature list
State what the user wants to accomplish, where they start and what a successful result looks like. A task such as “turn a saved note into a shared link” gives the sequence a beginning, middle and end. A list of every feature does not fit a short demo.
Name the exact interface labels that must remain visible. If a screen contains private names, email addresses, tokens or customer data, replace them before uploading the screenshot.
Use this editable brief
App: [name]. User task: [one task]. Starting screen: [screen]. Steps: 1) [action and label], 2) [action and label], 3) [result]. Important copy: [exact text]. Ending action: [what the viewer should do]. Use the supplied screenshots in this order: [file names].
Add a short note for each screenshot: what it proves, which area should be highlighted and whether the screen is allowed to be cropped. OneDollarVideo can use supplied images and documents as production material; it does not claim to crawl an app URL or create an unverified screen.
Check privacy and interaction accuracy
Review every screenshot for personal data and unpublished information. Verify that the labels in the brief match the actual interface. Do not describe a button as available if the provided screen does not show it.
For the public reference below, the original creator and post remain the source of the work. It demonstrates a visual direction for interface motion; it does not prove OneDollarVideo produced the app or the source video.
Related examples
These are related references, not outputs from this guide template.