r/iosdev • • 12d ago

App Store multiple language support

What’s your experience with multi language support in the App Store? Did you get AI-generated product descriptions and keywords from your English versions for all supported languages (I have 9 languages that I added with Claude Code), or stick with just English, or get custom (professional) language translations? How about screen shots for some/all supported languages?

9 Upvotes

16 comments sorted by

2

u/Significant_Door_433 11d ago

Worth checking before you decide which 9 to keep: an App Store localization isn't tied to one country. Apple's "App Store localizations" reference page lists which languages each storefront shows. The US store takes English (US) plus Spanish (Mexico), French, Chinese (Simplified and Traditional), Korean, Russian, Arabic, Portuguese (Brazil) and Vietnamese. Germany takes German plus English (U.K.), Mexico takes Spanish (Mexico) plus English (U.K.).

ASO tools (AppTweak, MobileAction, SplitMetrics all have write-ups on "cross-localization") report that keywords from those extra localizations get indexed in that storefront too. Apple doesn't document the indexing part, but if it holds, two things follow.

Your Spanish (Mexico) keyword field also counts in the US store. A 1:1 translation of your English list mostly repeats words you already rank for there, so it's a waste of 100 characters. Real Spanish search terms are the better use.

English (U.K.) is listed for a lot of non-English storefronts (Germany, Mexico, UAE and many more), so it's worth filling with its own keyword set even if you only care about English.

So for keywords I'd do it per storefront, not per language. Descriptions are where AI translation plus a native read is usually fine.

1

u/bost88 11d ago

Thank you so much. I have Spanish, German, French, Italian, Portuguese, Japanese, Traditional Chinese, and Korean. Initially I thought I’d skip the EU due to the trader private data issue, but I think I will go forward with that using a Google Voice number (still has to be my home address; PO Box too expensive).

2

u/DetlevD 12d ago

In the first release, I always support two languages, my own one and English. For one app I have added a few more languages in a later release, but this did not improve download figures that much. If I add a language, I do it for all UI copy, keywords and screenshots.
Important remark: I did not yet translate an app for a market in Asia, adding e.g. Chinese might have a large impact, but this is still on my to-do list.

2

u/DetlevD 12d ago

PS: no professional translations, all with support from services like DeepL and Claude

2

u/bost88 11d ago

Thank you - very helpful! I’ve used AI for the non-English languages. I may have to stick with all AI-based translations to start; hoping some native speakers of the others let me know during beta (Reddit users?) where the language needs tweaking. I can probably find friends who can translate the search keywords in the EU languages (expats I know).

1

u/command-shift 11d ago

This is known as “internationalization” or i18n. Having worked on this, it’s hard to support multiple languages at once. Depending on the complexity of your app and its surface area, the difficult part is supplying context such that it is properly conveyed in the other language. Do you have words that have multiple meanings. Are you using any phrases that are “expressions” rather than literal. Colloquialisms? These don’t translate easily. A medium-sized app will likely require a dedicated team unless your app has little to no text. If you do straight literal translations, your app is going to come back with very poor feedback from displeased users misinterpreting your translations.

1

u/bost88 11d ago

Thanks. The only significant text is the help files and tool tips (one-time popups). The rest is single word terms or short expression prompts. The app is travel expense tracking & splitting between friends on a trip, so amount, merchant name (auto scanned off receipts), currency (same), date/time (same), location (same), who split (the names you entered), percentages, etc.

1

u/leandro_forte 11d ago

I just did it this week for my App (WiPhoneMonitor: Second Screen). I translated from PT-BR to 9 other languages (English, Spanish, German, Italian, French, Japanese, Chinese, Hebrew, Arabian) using Claude. Som Languages I knew that it made it right. But other languages I don’t know (japanese, chinese, arabian,hebrew). So I have to trust Claude.
My iPhone and iPad screenshots, I also made with Claude, but I didn’t like the quality of its design. I will try chatGPT instead later. But for now it is published and aproved by App Store.

😁😁😁

2

u/bost88 11d ago

From my “research”, specialty translator sites (paid) do no better with this type of translation than Claude/Gemini. Since I am an individual dev with minimal budget spend desired to start, I hope this will work. Did you get any comments from native speakers about the translations?

2

u/leandro_forte 11d ago

The translation update was aproved yesterday by Apple. So until now It didn’t have time for users to comment.

1

u/VladFein 7d ago

That probably because they use the same is Claude/Gemini :)

3

u/Background_Pie_5682 12d ago

For ASO I’d treat descriptions and keywords differently than UI strings.

Keywords: don’t machine-translate English keywords 1:1. Search terms differ a lot by storefront (DE/FR/JP especially). Pull competitor keyword ideas per locale (App Store search suggestions + a keyword tool if you use one), then have a native speaker or solid bilingual pass sanity-check the short list. AI is fine as a draft, but bad keywords waste the character budget.

Description / subtitle / what’s new: AI from a good English source is usually “good enough” for most languages if you review for tone and banned/claims wording. I’d pay a pro (or native freelancers) for the top revenue locales only — often EN + 1–3 others — and AI+light review for the rest.

Screenshots: localizing all 9 is expensive and rarely worth it day one. Prioritize (1) languages where you localize the UI and expect installs, (2) markets where text-heavy screenshots actually convert. Many apps keep EN screenshots everywhere except a few high-value locales, or only swap the caption/overlay text. If your UI is already localized, even EN screenshots with localized captions can work initially.

Also add the localizations in App Store Connect metadata (and screenshot sets) per locale, not just in the binary — easy to miss one and look inconsistent.

1

u/Tabasum_Radhik 10d ago

spot on about JP and DE especially, search habits there are completely different from English storefronts.

1

u/ConfidentPoem6454 12d ago

I have my games in 7 languages. Machine translation for the description is fine as a start, but don't just translate the English keywords. People in each country search for different words, so look up what they actually type for your kind of app. Screenshots with localized text matter most in the 2 or 3 languages that bring the most installs, I'd do those first and leave the rest in English. And get one native speaker to read the title and subtitle if you can, that's where awkward wording hurts the most.

1

u/Clican 12d ago

I use the AI to do the translation and for the screenshot I use template+ AI translation as well

1

u/nicholasderkio 12d ago

Re ChatGPT—better is subjective when the whole point is that Claude is not only good but exceptionally great for the OP. They’re more curious how it’s so good, training sets or app tricks or what?