Shipshot guide

A practical app-store release checklist

Screenshots hold up more releases than they should, almost always because they are treated as the last task rather than a parallel one. The fix is ordering: certain decisions have to be made early because everything else depends on them, and certain checks can only happen at the end.

Freeze the message before the build is final

The caption copy depends on what the release actually does, not on its final polish. As soon as the feature set is settled, write the frame-by-frame message. This is the item that blocks everything downstream, because you cannot capture the right screens or brief a translator until you know what each frame is arguing.

  1. Write the one-sentence job of each frame as soon as scope is fixed.
  2. Circulate that list to whoever reviews copy before anyone opens an editor.
  3. Treat later message changes as a decision with a known cost, not a free edit.

Capture from a build that will not change again

Capturing from a moving build guarantees rework. Wait for the candidate build, then capture the whole set in one session so the interface, data, and device chrome stay consistent. If a late change alters a screen you already captured, recapture that screen from the new build rather than keeping a frame that shows an interface nobody will see.

  1. Capture only from the release candidate, not from a development build.
  2. Do the whole set in one session with one demo account.
  3. Recapture any screen a late change touches, and check its neighbours too.

Localize after the source copy is approved

Sending captions for translation before they are final is the most expensive ordering mistake, because every source edit multiplies across every language. Approve the source wording first, then produce the locale versions and review each one in place, checking that the layout still holds after the text changes length.

  1. Approve the source captions before any locale work begins.
  2. Review each locale in context rather than as a spreadsheet of strings.
  3. Check for clipping, overlap, and leftover source-language text in every version.

Leave the mechanical checks for last, and do them all

Dimensions, formats, alpha channels, counts, orientation, and file naming are the checks that fail an upload, and they are best done once at the end against the finished exports. Doing them earlier wastes effort on frames that may still change; skipping them entirely is how a release stalls on something trivial at the worst moment.

  1. Verify each exported file against the accepted dimensions for its target.
  2. Confirm formats and the absence of alpha channels across the whole export.
  3. Check counts and ordering per target and per locale before handing off for upload.

Review checklist

✓ The frame-by-frame message was fixed before capture began.✓ Every capture came from the release candidate build.✓ Source captions were approved before translation started.✓ Each locale was reviewed in place, not as a string list.✓ Dimensions, formats, counts, and naming were verified on the final exports.

Questions to ask before handoff

What is the earliest task in a screenshot release?

Deciding what each frame argues. Capture, design, translation, and review all depend on it, so it is the item that blocks the most work when it slips.

Can I start localizing before the copy is final?

It is the most costly ordering mistake available, because every source change repeats across every language. Approve the source first.

Who should do the final mechanical check?

Someone who did not build the frames. Familiarity hides missing files, wrong counts, and an unnoticed leftover from a previous release.

Share this guide