SynthMock
A messaging mockup needs believable conversation structure without exposing real conversations. This concept moves from a selected inbox thread to a larger view of that same exchange.
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.
Use a fictional thread with a simple purpose
Prepare a neutral exchange about planning a studio review. Use fictional participant names, original avatars or simple initials, and a few short messages. The cover can show the selected thread in the inbox; the inner screen can keep the conversation visible beside a restrained thread list.
A real notification, profile photo or address can survive in a screenshot long after the creator stops noticing it. Build demonstration content deliberately instead of blurring private conversations after capture. The campaign should not expose a person's contact details or imply that a fictional participant endorses the product.
Keep the conversation in the same state
The compact and expanded sources should agree on the selected thread, latest message and unread state. This small consistency check matters more to the story than adding many realistic-looking rows.
| Element | Cover | Inner view |
|---|---|---|
| Thread | Studio review selected | Studio review open |
| Latest message | A short meeting-time question | The same question visible in context |
| Supporting list | Only the most useful entries | A quiet list that does not overpower the conversation |
Show conversation structure, not private detail
For a proposed hero, keep the open screen close enough to frontal that message grouping and reply hierarchy remain clear. Small text need not be readable in every thumbnail, but the distinction between the list and the conversation should survive.
If adapting this direction to a real application, do not invent an expanded inbox layout or a cross-screen handoff that the product does not support. Use actual approved captures or label the work as an interface concept. A useful asset pair is a cover overview and an open conversation view, with a short caption explaining the relationship. Review both at normal page size and check every visible name, avatar and message before publication; the device framing does not make private source content safe to share.
Final pass
Before you call it finished
- Use fictional or explicitly approved conversation content.
- Match selected thread and unread state across both sources.
- Check names, avatars and message text in the final export.
Make the next version yours.
Explore Duo templates ↗