2026-04-20 · 4 min read
After two releases where screenshot fixes delayed launch by hours, we stopped improvising and created a strict checklist. It is not glamorous, but it saved us repeatedly.
1) Lock scope first. Confirm platforms, device sets, locale list, and screenshot count per locale. If this moves late, every downstream estimate becomes fiction.
2) Run a capture dry run at least one day early. The goal is not final assets. The goal is to catch broken deeplinks, login states, and missing seed data.
3) Freeze copy by timestamp, not by verbal agreement. We use one shared sheet with a clear lock time so nobody edits text during export unless there is an explicit exception.
4) Validate the two hardest locales first. We normally pick German and Japanese because they expose opposite layout risks: overflow and density.
5) Batch review by screen index, not by language. You will catch consistency issues faster when the same screen is viewed across all locales in sequence.
6) Export to marketplace-ready naming in one pass. App Store and Google Play rules are close but not identical, so naming should be automated, not manually renamed.
7) Run a final smoke check on the exported folder. We verify count, dimensions, sequence order, and a random spot check on copy.
8) Keep a fallback package. If a late blocker appears, we can still ship with a known-good set instead of restarting from zero.
The headline is simple: checklist discipline beats heroic all-nighters. Most screenshot failures are process failures you can prevent earlier.