SynthMock
A public template preview helps someone decide whether the composition fits their project. Editing and export are separate actions with their own access requirements. Clear expectations make the handoff more useful for everyone involved.
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 the preview to make a creative decision
Before preparing a full set of source files, inspect the template's device, fold, camera and screen emphasis. Decide whether it gives your product enough readable space. A beautiful template can still be the wrong starting point for a dense interface or a particular delivery format.
Public viewing does not create an owned project or grant unrestricted native export. In SynthMock, using or editing native templates and exporting images or videos requires signed-in paid access. State that distinction when sharing a template with a colleague or client so the next step is understandable before they invest effort.
A simple expectation map
The useful question is what the recipient wants to accomplish. Match the link and explanation to that purpose instead of using the word share for every stage.
| Purpose | What to expect | What not to assume |
|---|---|---|
| Inspect a composition | A public preview where sharing remains enabled | An editable project has already been created |
| Adapt it to your app | An authorized template-use flow into an owned project | A free preview includes native editing |
| Deliver images or video | Paid native export and supported output workflow | Viewing a link grants export access |
Make shared links resilient to change
A template owner can change or revoke sharing. If a specific link no longer works, return to the current collection rather than assuming the browser is broken. When preparing a campaign handoff, verify the shared destination shortly before sending it and label a collection link as a collection, not an exact scene.
Ordinary shared links and custom short links also have different permissions. Custom vanity addresses are an admin capability; other creators should not plan a handoff around claiming a short path. Keep the communication focused on the recipient's next action: preview the direction, choose a template, or continue in their own project. Honest labels reduce confusion more effectively than promising a frictionless workflow that ignores account or plan requirements.
Final pass
Before you call it finished
- Explain preview, adaptation and export separately.
- Verify the shared link remains active.
- Use accurate labels for a collection versus a specific template.
Make the next version yours.
Explore Duo templates ↗