Architecture Notes
1.2.3 · Dev Platform

How to Localize App Screenshots Without a Mac — Use Every Trick at Once

2026.07.12~5 min

00Overview

01Story

Situation

By 1.2.2, all the text — app and listing — is localized. What remains is the screenshots.

Complication

Properly, you'd boot an emulator on a Mac and automate screenshots across language switches. But as 1.1.2 established, there is no Mac at hand. Producing screenshots for fifty locales looked impossible through any single method.

Question

Without a Mac, how do you produce screenshots in dozens of languages?

02Solution

Criteria

  • Works without owning a Mac
  • Covers a large number of languages
  • Meets Apple's strict size requirements

Answer

Instead of forcing one method to do everything, use all four at once:

  • Design the UI to be as language-independent as possible — every word removed from an image is a word that needs neither translating nor generating.
  • Shoot major languages (Japanese, English, …) on the real device — switch the language, take real screenshots.
  • Batch-convert the rest with Flow — "make this image the X-language version," in bulk.
  • Draw annotations onto the English set and reuse it — with illustrations and callouts in place, the details don't need remaking per language.

The generated images are zipped and uploaded to Git, unpacked and arranged by Claude, then sent to App Store Connect by GitHub Actions (split, crop, resize, and up through the store's API).

Reason

Because only a combination clears the no-Mac constraint. Shoot everything on-device and the effort scales with the language count until it crushes you; generate everything with AI and the details smear while the size requirements slip.

Any one method fails.
Together, they clear it.

Flow deserves a special mention: it generates large batches at once, downloads them as a ZIP, and lets you queue the next batch while one is rendering. The throughput is a gift.

Options

  • Shoot everything on a real device — faithful, but the effort scales with every language. Not realistic.
  • Generate everything with AI — fast, but details break and Apple's strict sizes are missed. Hence: use everything.

03Result

Good

Multilingual screenshots, no Mac involved. The language-independent UI and the annotated-English reuse also shrank the sheer volume that needed generating. A mountain of dull work now turns over smoothly with AI in the mix.

Bad

Apple's screenshots fail to upload if the size is off by a single pixel. That one adjustment sits beyond what AI absorbs, so a human finishes it by hand. Knowing where automation ends is part of the design.

Follow-up

With app, listing, and screenshots all localized, the product is ready for a worldwide release. Where to aim it — the idea that a narrow niche becomes a market when the world is the denominator — continues in 3.1.2 STP.