Android Builders Weblog: Per-App Language Preferences

// Utility methodology to place a string in a SharedPreference non-public enjoyable putString(key: String, worth: String) {     val editor = getSharedPreferences(PREFERENCE_NAME, PREFERENCE_MODE).edit()     editor.putString(key, worth)     editor.apply() } // Utility methodology to get a string from a SharedPreference non-public enjoyable getString(key: String): String? {     val desire = getSharedPreferences(PREFERENCE_NAME, PREFERENCE_MODE)     return desire.getString(key, null) }

// Verify if the migration has already been performed or not if (getString(FIRST_TIME_MIGRATION) != STATUS_DONE) {    // Fetch the chosen language from wherever it was saved. On this case it’s SharedPref    // On this case let’s assume that it was saved in a key named SELECTED_LANGUAGE   getString(SELECTED_LANGUAGE)?.let { it →       // Set this locale utilizing the AndroidX library that can deal with the storage itself       val localeList = LocaleListCompat.forLanguageTags(it)       AppCompatDelegate.setApplicationLocales(localeList)       // Set the migration flag to make sure that that is executed solely as soon as       putString(FIRST_TIME_MIGRATION, STATUS_DONE)   } }

What flexibility does the function present to the customers and builders?

Right here are some things that may show to be useful for you customers.

1. All units working Android 13 or greater may have a typical place for customers to find and alter the language of their apps.
2. Though the system settings are restricted to the units working Android 13 or greater, the AndroidX APIs are backwards appropriate. Thus, there isn’t any requirement so as to add OS Model checks in your code whereas constructing on your multilingual customers.
3. Builders don’t must deal with configuration adjustments individually or fear about storing the person’s chosen language each time. The API handles configuration adjustments and shops the language preferences for you.
4. Works with different Android options like Backup and restore. If a person switches to a brand new gadget and restores the beforehand backed up information, your app will retain the person’s final most well-liked language, thus offering your customers with a greater and extra seamless expertise.

Recap

With that, most components of the function are coated. So let’s have a fast recap on what we mentioned in immediately’s learn.

1. A fast learn on what Per-App Language Preferences provide to multilingual customers and app builders.
2. What finish customers will see on their units.
3. Learn how to migrate your app to the Per-App Language Preferences APIs.
4. A number of issues that should be taken care of whereas migrating to the APIs to make sure a greater person expertise.
5. Lastly, the advantages that finish customers and builders can leverage from this function.

References

1. Per-App Language Preferences
2. Pattern App ( Compose )
3. Pattern App ( Views )
4. Per-App Language Preferences (YouTube Video)