Plan the output matrix
List the stores, device families, languages, and page messages required for the release before creating the project. This prevents a polished phone design from becoming an accidental template for incompatible desktop or television outputs.
Presets define dimensions and format rules. They do not force every target into a separate design, and they do not make every page mandatory.
- Start with the stores you will actually publish to.
- Choose one representative size for initial composition.
- Keep the first release matrix intentionally small.
Create the project
Choose the target stores and presets, then name the project for the app and release stream it represents. The project keeps pages, managed assets, languages, target selection, and output settings together.
Imported assets are copied into the managed project directory by default, so the composition does not silently depend on a temporary Downloads path.
Build the first page
A page combines one background with an ordered list of screenshot, image, text, shape, group, and device-frame layers. Start with the application capture and its single strongest message before adding decoration.
Name the page for its product claim, not its position. A name such as Fast capture remains useful when the page order changes; Screenshot 2 does not.
- Keep shared logos and decorative assets in the project library.
- Use groups for elements that should move together.
- Use a device frame only when it improves recognition.
Use normalized geometry
Layer position and size are stored relative to the canvas. This lets one composition adapt across compatible outputs while text scales from a design reference width.
Treat normalized geometry as the shared rule and add per-size overrides only when a real aspect-ratio, safe-area, or hierarchy problem appears.
- Align important content to stable guides.
- Avoid tiny fixed offsets that only look correct at one size.
- Preview the largest and smallest selected outputs before continuing.
Duplicate and vary intentionally
Duplicate a strong page when the layout remains useful but the message or capture changes. Keep common brand treatment consistent, then make the minimum content changes needed for the next product claim.
Do not duplicate entire pages merely to handle a language or output size. Languages and per-size overrides exist specifically to prevent that maintenance problem.
Save, recover, and hand off
Edits autosave through the local project database, while recovery snapshots preserve unsaved editor state after an interruption. A successful save commits the serialized project and clears obsolete recovery data.
For handoff, use the portable project workflow rather than copying individual rendered images and hoping the next editor can reconstruct the design system.
- Resolve a recovery prompt before making new edits.
- Keep project-owned source assets with the project.
- Export final output separately from the editable project.