Apple: App Store Connect adds 11 new metadata localizations (now 50 total)

Original announcement (source): Apple Developer News - “App Store expands support to 11 new languages” (published March 31, 2026)

• https://developer.apple.com/news/?id=97t4mt64

The headline

App Store Connect now supports localized metadata for 11 additional languages, taking the total supported localizations to 50.

New languages: Bangla, Gujarati, Kannada, Malayalam, Marathi, Odia, Punjabi, Slovenian, Tamil, Telugu, and Urdu.

Why this matters (beyond “nice to have”)

Localization is usually treated as translation work. Apple is reminding us it is a relevance lever:

• localized app name and subtitle shape search and browse relevance,
• localized screenshots shape conversion (especially when expectations are cultural, not just linguistic),
• localized badges reduce trust friction in ads, web, and email.

If you are expanding in India, this is an immediate opportunity because these languages often represent users who are not served by English-first metadata.

What to do now

1) Do not localize everything at once

Start with the highest-impact pieces:

• app name and subtitle (clarity beats creativity)
• screenshot #1 promise (one clear job-to-be-done)
• short description equivalents where relevant

2) Tie localization to intent, not geography

If you already run custom product pages (CPPs), treat language variants as another dimension of “match the promise to the search.”

3) Use the new localized App Store badges everywhere

If you have paid social, influencer content, or landing pages, swapping badges is a cheap win for credibility.

Tiny win

Pick one of these 11 languages where you already have meaningful installs. Localize just:

• screenshot #1 headline, and
• the first 2 lines of your description.

Then watch conversion rate for two weeks before you translate the rest.

Read the original: https://developer.apple.com/news/?id=97t4mt64