Plan App Screenshot Exports with a Release Matrix

Start with the combinations you intend to publish

For a simple example, five frames across three targets and four languages produce sixty output images. That does not mean you need sixty independent designs. It means sixty combinations need to be complete and reviewed. If the Android listing uses four frames while the Apple listing uses five, calculate each target separately and add the totals. Do not multiply by every format a tool supports when your app will only ship to two of them.

1. List each store and device class as a separate row.
2. For every row, record the intended frame count and supported listing languages.
3. Calculate the sum of frames multiplied by languages for each target.

Track source captures separately from composed artwork

One localized capture may appear in several export sizes, while a tablet target may need a different interface entirely. Add columns for raw capture ready, caption approved, layout checked and export reviewed. This distinction prevents a translated caption from being mistaken for a complete localized screen. A screenshot containing English UI text still contains English pixels after the surrounding title has been translated.

1. Assign each raw capture a locale and a screen identifier.
2. Mark reused source images explicitly rather than copying files into ambiguous folders.
3. Flag targets that need a distinct tablet or platform capture.

Give each incomplete cell an owner

A red cell labeled “French missing” does not tell the team what to do. “French search caption awaiting review” and “French tablet capture needs the release build” describe different tasks with different owners. Add a reviewer and a short blocker note. Keep draft, approved and uploaded states distinct so an export is not treated as a successful store handoff. This is especially useful when design, translation and release work happen on different days.

1. Choose one person to resolve the final approval state for each language.
2. Keep file checks separate from language approval.
3. Record the upload date only after checking the corresponding store preview.

Use the matrix to control late changes

When a caption changes, identify all targets and languages that inherited it. When a source screen changes, locate every composition that uses it. Reopen only the affected approvals, but do not assume an old export was refreshed just because the source project looks correct. Generate new files, compare them with the approved change and mark the corresponding cells complete. Keep the previous matrix as a release record rather than overwriting the evidence of what shipped.

1. In Shipshot, preserve editable captions and review each affected target after a change.
2. Inspect the downloaded file names and dimensions against the planned matrix.
3. Archive the approved source project and final export set together for the next release.

Review checklist

Questions to ask before handoff