Part 4 of 12 ✶ Translating your app People are sleeping on translating their app.

When I launched my app, it was only in English. And once I translated it, my downloads jumped 30% because over half my users aren't in the US. This is part four of 12 on how I run my apps. Now the problem is translating an app is a lot of work. Getting AI to translate words is pretty easy, but I had to do it in every screen in my app and across 144 App Store screenshots

and nine separate App Store listings. So here's how I do it. I have Codex handle all of it as one workflow. For the screenshots, Codex uses computer use to control Figma and it runs a custom plugin that swaps every translation into my existing iPhone and iPad layouts. For the App Store listings,

it uses something called the App Store CLI, which allows it to translate the description and keywords in each language and upload all 144 screenshots. And inside the app, Codex moves every string into Xcode string catalogs. It fixes hard-coded English

and layouts that break with longer text. Then it tests every language in the simulator. Now it's a pretty slow process and the first pass did take Codex a couple hours to do, but then every update just takes a few minutes. This used to be really hard two years ago, but now it's super easy, so there's no reason not to do it. This is part four of 12 on how I run my apps.

Follow along for part five where we talk about how I prevent outages.

Follow along for part five where we talk about how I prevent outages.

where we talk about how I prevent outages.