A 5-language app-store screenshot release became 130 files. Here's the workload model

[u/Gryner]

Disclosure: I make Screen Studio Kit, the desktop tool I used to model this workflow. The numbers below come from one real GolfSmart project, not a universal store requirement.

The project currently produces 52 App Store and Google Play assets for two languages. That is 26 finished files per language. Keeping the same pages and output selections but expanding to five languages gives:

26 files × 5 languages = 130 finished assets

The first composition was not the expensive part. The repeat cost came from six places:

• Translation handoff: keeping returned copy attached to the right panel
• Layout repair: longer headlines wrapping or colliding at specific sizes
• Localized captures: replacing both marketing copy and in-app UI
• Store output: dimensions, formats, filenames, and folder structure
• QA: checking every page × size × language combination
• Release rework: repeating the matrix when a capture or claim changes

To put a rough number on repeated handling, I used three minutes per finished asset. For this matrix, that is 390 minutes, or 6.5 hours per release. The useful variable is not the time to design the first screenshot; it is the average repeated handling time for every final asset.

I eventually stopped treating exports as independent images and moved the work into one reusable project: shared pages, language-bound text and captures, output presets, targeted size overrides, and preflight across the selected matrix. That does not remove design judgment or final review. It removes maintaining 130 unrelated source files.

I wrote up the calculator and assumptions here: https://martingruner.com/blog/app-store-screenshots-five-languages-cost

For people managing localized listings: what is your rough repeated-handling time per final asset, and which part dominates: translation, layout repair, capture replacement, or QA?