OOmnistu

Blog / Mobile App Development

Mobile App Development

App localization that respects the user: per-app languages on Android and iOS

Android 13's per-app language settings and LocaleManager APIs, iOS per-app preferences, and the unglamorous work that matters more: externalized strings, pseudolocales and plural rules.

OOmnistu
Reviewed 2026-11-19 · 3 min read

Half your potential users may prefer an app in a language that is not their phone's system language - think of a Hindi speaker whose work phone is set to English. Until recently, Android apps inherited the system language and users had no per-app override. Android 13 changed that with per-app language preferences, and Apple has offered per-app language settings since iOS 13. Supporting both well is now a small amount of platform work plus the slower work of actually translating your strings.

What Android 13 gives you

Android 13 introduced two things for multilingual users. First, a centralized place in system settings where users can select a preferred language for each app. Second, public APIs - setApplicationLocales and getApplicationLocales in LocaleManager - that let an app set a runtime language different from the system language. These APIs automatically sync with the system settings, so an in-app language picker built on them stays consistent with whatever the user picked in settings.

The implementation path is short for new projects. Starting with Android Studio Giraffe and AGP 8.1, the build system can generate per-app language support automatically from your project's resources - you will not see an android:localeConfig manifest entry or a res/xml/locale_config.xml file because they are produced at build time. Older projects can declare the locale config by hand. If your picker uses AppCompatDelegate.setApplicationLocales for backward compatibility, call it the first time the app runs on an Android 13 device so pre-existing user choices reach the system, and note that the APIs support Auto Backup so a user's language choice survives a phone change.

The iOS side

On Apple platforms the machinery is different but the principles match. Users can set a preferred language per app in system settings. Your job is to externalize every user-visible string, localize assets in the asset catalog (image sets, symbol directionality for right-to-left languages like Arabic and Hebrew), and lean on the Foundation framework to format user-visible and dynamic values - dates, numbers, currencies - correctly for each locale. SwiftUI and Auto Layout handle much of the layout adjustment, including right-to-left mirroring, provided you have not hard-coded widths or leading/trailing assumptions as left/right.

The work that is not platform setup

Externalize before you translate. Every string a user can see belongs in a resource file, including plurals and formatted strings. Concatenating translated fragments ("You have " + count + " messages") breaks in languages with different word order and plural rules; use format strings with placeholders instead.

Test with pseudolocales. Android Studio can generate pseudolocales - fake translations that pad strings with accented characters and expand their length. Running the app in a pseudolocale catches hard-coded strings, truncation and layout breaks before a translator ever gets involved. German-length text (often a third longer than English) and a right-to-left locale are the two cheapest real tests after that.

Ship languages incrementally. Both platforms fall back to your default language for missing translations, so a partial translation is shippable. Be deliberate about which screens go first: onboarding and checkout errors in the user's language are worth more than translated settings screens.

Store listing and legal text. A localized app usually wants a localized store listing and localized privacy policy. Plan those together with the app strings; an app store page promising a language the privacy policy does not offer is an avoidable complaint.

Where to start

Enable AGP's automatic per-app language support, externalize every string, add the pseudolocale to your test routine, then commission one high-value language end to end - strings, store listing, policy. The platform pieces are a day or two of work; everything else is process.

Sources

Prepared with AI assistance and reviewed before publication. Platform features described from Google's and Apple's documentation, checked on 19 November 2026.