SynthMock
A scheduling concept can use the cover for the next commitment and the inner screen for surrounding context. The challenge is making that relationship obvious without turning the larger screen into a wall of tiny events.
Try it in SynthMock
Start with a Duo scene.
Use a reusable template as your starting point, then apply the choices in this article.
A paid plan is required to use templates and export.
Make one event the bridge
Use a fictional event such as Studio review at 10:00. The cover identifies it as the next item. The inner layout shows that same event selected within a day or week. Keep the date, duration and time zone consistent, even when the surrounding layout changes.
Do not populate the source with real meeting links, attendees or private client names. A short set of original demonstration events is enough to explain the product. If the campaign represents a real application, use its actual supported calendar modes rather than assuming the larger display automatically creates a week view.
Choose day or week for a reason
A wider view is not automatically a reason to show more days. Compare the following directions with the actual source and delivery size.
| Direction | Useful message | Main tradeoff |
|---|---|---|
| Expanded day | Understand the next event in a manageable schedule | Less long-range context |
| Week overview | See the selected event among several days | Smaller labels and more visual density |
| Event detail with context | Understand one commitment and its surroundings | Less emphasis on the overall calendar |
Keep the time structure readable
For the first rough, use an open view with restrained roll and perspective. Strong diagonal framing can make the calendar's own grid compete with the device angle. Let the layout establish the rhythm before adding a more expressive camera treatment.
A proposed motion sequence begins on the selected event, opens into the chosen context and finishes with the event still easy to locate. If fine labels are essential, deliver a companion detail instead of extending the animation with repeated close passes. Inspect the exported view at its normal page size, checking that the event remains identifiable and that the source data agrees across screens. The finished mockup should explain a planning experience, not simply demonstrate how many boxes fit inside the device.
Final pass
Before you call it finished
- Match date, time zone and selected event across screens.
- Choose day or week according to the message.
- Keep real meeting links and personal details out of demo sources.
Make the next version yours.
Explore Duo templates ↗