Skip to main content

 

Mastering Per-App Language Preferences: From Android 10 to Android 13+

One of the most requested features by users is the ability to use an app in a language different from the system language. While Android 13 (API 33) introduced "Per-App Language" settings at the system level, implementing this backward-compatibly for older devices like Android 10 (API 29) used to be a challenge involving manual configuration wrapping.

Today, thanks to AppCompat 1.6.0+, we have a unified, standard way to handle this. Here is the modern guide to implementing seamless language switching.


The Architecture: How it Works

On Android 13 and above, the system handles the storage and application of your app's locale. On older versions, the AppCompat library manages this behavior by storing your preference in an internal XML file and injecting the resources during the activity lifecycle.


Step 1: The Locale Helper Utility

Instead of scattering logic across your app, use a clean LocaleHelper object. This handles the distinction between the system LocaleManager (API 33+) and the library AppCompatDelegate (Legacy).

Kotlin
object LocaleHelper {
    /**
     * Applies the chosen language code (e.g., "en", "hi", "es") 
     */
    fun applyLanguage(context: Context, languageCode: String) {
        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) {
            // Android 13+ (System level support)
            val localeManager = context.getSystemService(LocaleManager::class.java)
            localeManager.applicationLocales = LocaleList.forLanguageTags(languageCode)
        } else {
            // API 29-32 (Library level support via AppCompat)
            val appLocale: LocaleListCompat = LocaleListCompat.forLanguageTags(languageCode)
            AppCompatDelegate.setApplicationLocales(appLocale)
        }
    }

    /**
     * Detects the currently active language
     */
    fun getActiveLanguage(context: Context): String {
        val locales = AppCompatDelegate.getApplicationLocales()
        return if (!locales.isEmpty) {
            locales[0]?.language ?: "en"
        } else {
            // Fallback to configuration for first-time launch
            context.resources.configuration.locales[0].language ?: "en"
        }
    }
}

Step 2: The Crucial Manifest Requirement

For versions below Android 13, AppCompat needs a way to "remember" the language choice after the app is killed or the device is restarted. You must declare this service inside your <application> tag in AndroidManifest.xml.

Without this, your language settings will reset every time the app closes on API 29.

XML
<application ...>
    
    <service
        android:name="androidx.appcompat.app.AppLocalesMetadataHolderService"
        android:enabled="false"
        android:exported="false">
        <intent-filter>
            <action android:name="androidx.appcompat.app.AppLocalesMetadataHolderService" />
        </intent-filter>
        <meta-data
            android:name="autoStoreLocales"
            android:value="true" />
    </service>

</application>

Step 3: Implementation in MainActivity

When using Jetpack Compose or View-based activities, ensure your activity inherits from AppCompatActivity. This is vital because AppCompatActivity contains the logic to intercept and apply the localized resources.

Kotlin
class MainActivity : androidx.appcompat.app.AppCompatActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        
        setContent {
            // Detect current language using our Helper
            val currentLanguage = remember { LocaleHelper.getActiveLanguage(this) }

            MainAppScreen(
                currentLanguage = currentLanguage,
                onLanguageChange = { newLang ->
                    // The library handles activity recreation automatically
                    LocaleHelper.applyLanguage(this@MainActivity, newLang)
                }
            )
        }
    }
}

Step 4: Enabling System-Level Settings (Android 13+)

To allow users to see your app's language options directly in the Android System Settings, you must provide a locales_config.xml.

  1. Create res/xml/locales_config.xml:

    XML
    <?xml version="1.0" encoding="utf-8"?>
    <locale-config xmlns:android="http://schemas.android.com/apk/res/android">
       <locale android:name="en"/>
       <locale android:name="hi"/>
       <locale android:name="es"/>
    </locale-config>
    
  2. Link it in Manifest:

    XML
    <application
        android:localeConfig="@xml/locales_config"
        ...>
    </application>
    

Summary Checklist for Success

  • Library Version: Use androidx.appcompat:appcompat:1.6.0 or higher.

  • Activity Type: Use AppCompatActivity for full backward compatibility.

  • Persistence: Verify the AppLocalesMetadataHolderService is in the Manifest.

  • No Manual Recreate: Calling setApplicationLocales() triggers an automatic, optimized activity recreation. You do not need to call recreate() manually.

By following this standard approach, you provide a premium, localized experience for all users—whether they are on the latest Android 16 or a legacy Android 10 device.

References:

https://developer.android.com/guide/topics/resources/localization

Comments

Popular posts from this blog

Firebase with android: An Overview of Products and Usage

Introduction: In the evolving landscape of mobile application development, understanding user behaviour, managing user identity, and delivering personalised communication are critical components of a successful digital product. Google provides a suite of powerful tools through Firebase and Google Analytics that help developers build, improve, and grow their applications efficiently. This article explores Google Analytics , Firebase Authentication , Firebase Cloud Messaging (push notifications), and other core Firebase products , along with their practical uses. Google Analytics Google Analytics for Firebase is a free app measurement solution that provides insights on app usage and user engagement. Unlike traditional Google Analytics, this version is tightly integrated with Firebase services, making it highly useful for mobile and cross-platform apps. Key Features: Event tracking : Automatically or manually track user actions like screen views, button taps, purchases, etc. User segm...

Android Studio Release Updates

JetBrains's  Android Studio’s 10 year anniversary      I remember the major change which has taken place since I started learning android is Android Studio migration from Eclipse. Android Studio’s 10 year anniversary. Watch official youtube : Android Studio’s 10th birthday: our favorite moments!      In December 2014 , Google launched Android Studio, Google's official Integrated Development Environment (IDE) based on IntelliJ and it discontinued the Android Developer Tools (ADT) plugin for Eclipse, which means it’s time to leave eclipse behind.        Fortunately, we had simple solution to migrate, Android Studio offered a better experience for Android developers and its migration functionality does most of the work for you.      Open Android Studio and click on the option:  Import project (Eclipse ADT, Gradle, etc) Before Android studio      1. users had to go download a JDK, then download Eclipse...

Google re-branded the support Android libraries to AndroidX

It is important to note, you cannot mix AppCompat and Jetpack in the same project. You must convert everything to use Jetpack if you want to upgrade. The support library artifacts are being deprecated and all future development is going into AndroidX , so there's no avoiding this migration. Alan Viverette sums this up nicely: “There won’t be a 29.0.0, so Android Q APIs will only be in AndroidX” The stable release of 28.0.0 will be the final feature release packaged as android.support . All subsequent feature releases will only be made available as androidx-packaged artifacts. Below tips will give you a clearer transition path. The current version of AppCompat (v28.x) is exactly the same as AndroidX (v1.x). In fact, the AppCompat libraries are machine generated by changing maven coordinates and package names of the AndroidX codebase. For example, android.support.v7.app.AppCompatActivity is now androidx.appcompat.app.AppCompatActivity For a complete listi...