Who this is for: Teams showing cross-device product tasks.
What to prepare
- Mobile capture states
- Desktop arrival evidence
- Verified handoff prerequisites
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Plan a 30-second illustrative sequence for sample observation N-017, “Sample shelf note.” Start in the actual mobile interface labeled “Example observer — Mobile.” Show the supplied capture and save or submit states with the same title and sample image. Distinguish a local draft from a successfully transferred item using the product’s real status. Use an explicit handoff, “Later, in the same sample workspace.” On desktop, label “Example reviewer — Desktop,” locate N-017 or its matching visible identity and open it. Hold the matching image and title before showing the actual review action. End on confirmed review status only if supplied. Do not suggest Animro performs mobile capture, imports observations or synchronizes these tools. This describes the reader’s demonstrated product using provided assets.
Make it your own
- Object identity
- Use matching title, image and identifier where available.
- Actors
- Label both device and role.
- Transfer condition
- State actual connectivity, sync or manual steps.
Match the object
Supply authentic mobile and desktop views of the same illustrative content. If the product does not show identifiers, use a real title-and-thumbnail combination. Do not create a new UI field solely to make continuity easier.
Adapt the layout
A brief side-by-side hold can establish the match in a wide composition. In a narrow video, show the devices sequentially and retain the title through the transition. Keep one active device during each action.
Correct transfer assumptions
If the workflow requires a manual upload or refresh, include it. Replace an instant screen morph with a labeled cut when elapsed time is unknown. If only a local save is evidenced, narrow the ending to that state instead of asserting desktop arrival.
Review checklist
- The object matches across devices.
- Local and transferred states are distinct.
- The handoff has explicit actor and device labels.