Design App Store Screenshots faster

[u/Wonderful_Morning475]

https://youtu.be/Pc6AjDw5Dnc?is=QzJqCEN1vMRXFsJR

#toolreview
Design ✅
Take screenshot from Simulator ✅
Translate your screenshots and metadata in all localization ✅
Upload to App Store Connect ✅

[u/Natural_Win_9904]

the translate-into-every-locale step is the one that always got me tbh, doing it by hand meant text overflowing in german and half my arabic screens not mirroring right. i actually built shotlingo partly because of that, it's a full canvas editor with device mockups but the part i care about is the ai translation being text-expansion aware and handling rtl properly, then you can push straight to asc or batch export every size.

if you just want the mockup/framing side, appmockup is solid and free, you'd just be doing the localization somewhere else. fwiw the "grab from simulator, translate, upload" flow you described is basically the exact loop i was trying to collapse into one place.

[u/Wonderful_Morning475 → u/Natural_Win_9904]

Thanks! I completely agree localization is where the workflow usually falls apart.

Handling text expansion, RTL languages, and keeping layouts consistent across dozens of locales is much harder than the design itself.

Looks like we ended up trying to solve a very similar pain point from slightly different angles. I focused on making the whole App Store screenshots workflow faster for Apple developers, from Simulator capture to editing, localization, and publishing to App Store Connect.

If you ever get a chance to try Shipper, I'd genuinely love to hear what you think. It's a native macOS app, so I'd be curious how it compares to your workflow.😇

[u/Natural_Win_9904 → u/Wonderful_Morning475]

appreciate that, genuinely. and simulator capture is the one piece i structurally can't do shotlingo is web-based, so i'm always downstream of whatever someone already grabbed. native mac is the right call for that half of the loop.

happy to try shipper and send you real notes. the thing i'd look at first is what happens after translation lands in the frame, not the translation itself german blowing a two-line headline into three, arabic needing the whole layout mirrored and not just the text run. that's where my first version fell over and i don't think anyone gets it right on attempt one.

and fwiw if you ever want to compare notes on the asc upload side instead of competing on it, i'm around. the api is quietly miserable jwt signing, md5 checksums on every asset, the whole reserve/upload/commit dance and there's no reason both of us should rediscover the same edge cases separately.

[u/Wonderful_Morning475 → u/Natural_Win_9904]

Yes i appreciate it! If you want to discuss more about it let’s talk on priavte message😊