- Release Notes
- Get Started
- Project Planning
- Account Settings
To facilitate and speed up the demo creation process, select and prepare all media assets in advance.
Assets typically include video files with action sequences, finger tap or arrow animations and sounds, images, sound effects, background music, instructional text with effects, and so on. Additionally, you will need to identify desired user interactions and transition logic for the selected scenes.
To select videos for an app or game demo:
- Skip any tedious or dull sections with repetitive activities such as farming or building.
- Make a list of possible candidates by identifying sections of the app or game that are:
- Representative of the app features
- Most interactive and exciting
- Simple enough to be repurposed as a demo
- Estimate the length and size of your demo, for example, by determining:
- How many loop-gesture-action sequences you want to include.
- How many moves/interactions a user will make.
- How many characters you want to include in the demo, if applicable.
Tip: The fewer characters and alternate paths you make, the fewer videos files you will need to make and prepare. We recommend a maximum of two characters.
For more sophisticated transition logic, with decision points for alternative paths, you can outline your desired flow by creating a flowchart and then use it to figure out what additional media assets you may need. For example, the baseball flowchart below indicates the need for four additional assets if one of its transitions is randomized.
Your flowchart doesn’t have to be a formal, detailed outline of all possible permutations. Figuring out your overall desired demo flow, however, will also come in handy when you start creating a storyboard, which can be just as informal.
Tip: You can scribble your diagram on paper. You will decide on how to implement logic for each decision point later, after you learn about Advanced Transitions, Triggers, Counters, and Logic-Only Scenes. For now, focus on identifying the media assets you need.
Make a List
After you have decided which scenes to include in the demo, make a detailed list of other assets that you think you will need for your demo. For example, your final list for a basic on-rails demo may include the following items:
- Videos that will play continuously (loop) until the user makes a move.
- Action videos that will follow each move/gesture.
- Types of gestures to be used in each scene for transitions.
- Sound effects to accompany each user action, for example, tap or click sounds.
- Animations or other visual effects to prompt users to perform each gesture.
- Images of buttons, such as call-to-action, and buttons to allow the user to close, replay, or skip parts of the demo.
- Images of icons for any static elements, for example, to display counter values, or any other items that you may need to use in the demo.
- Logos and any branding images.
- Background music to accompany specific scenes or the entire demo.
- Splash screen video.
- End card video.
After you make a list of the required assets and have an idea of your demo flow, you may start creating your storyboard and preparing your assets.