App language settings: make the scope clear

Say which language the setting controls

Reverso labels its picker Interface Language. AI Phone labels App Language and explains that the choice applies to menus and dialogs. That extra scope is useful because a communication product can also handle the language of a call, translation or transcript. The interface language is not a substitute for any of those content choices.

Use the same scope in the settings row, picker heading and confirmation. Avoid calling it App language on the first screen and Preferred language on the next if those terms could imply different effects. If a restart is genuinely required, explain what will happen before applying the change and preserve the task the person was completing.

Do not rewrite saved content when changing interface locale. Existing notes, messages and user-created titles should retain their original text unless a separate translation action is requested. An interface preference can update date or number presentation, but that formatting must not silently alter the stored value. Keep the distinction between presentation and source content explicit in the implementation.

Help people recognize a language they can read

HelloTalk combines native-script names, flags and an OK action. ChatGO uses native language names and distinguishes Portuguese variants. Native names can help someone recover from an unfamiliar interface, but flags should remain secondary. A country is not a language, and several countries may share one language while one country uses several.

Use native language names as primary identifiers where possible, with a localized or widely recognizable secondary name when useful. Keep text readable across scripts and allow rows to grow for longer labels. A fixed-height row that clips a regional distinction can make two different options appear identical. Search should match native and supported alternate names, not just the current interface translation.

Show the selected state with a check and an accessible state announcement, not color alone. If the list scrolls, reveal the current choice or provide a quick route to it. Test recovery from a language the tester cannot read: can they locate settings, identify the language control and select a familiar option without relying on memorized row positions?

Only offer distinctions the product actually supports

Arch presents a bold native name above a secondary English name. Lightly explicitly says its setting changes both the app interface and AI communication. These are different kinds of specificity: identifying an option clearly and identifying the consequences clearly. Both matter more than the number of choices in the list.

Offer a regional variant when there is a meaningful supported distinction, such as translated vocabulary, formatting or content requirements. Do not display a long list of locales that all fall back silently to one incomplete translation. If only a general language is supported, label it honestly. If a specific variant falls back, make that behavior understandable rather than implying full localization.

When interface and AI response language are coupled, disclose the coupling and consider whether people need separate controls. A bilingual person may want familiar navigation with output in another language. Changing the interface should not unexpectedly alter the next generated response unless that relationship is part of the product’s stated behavior. Existing conversations should keep their own context.

Choose immediate switching or explicit application

GentleFit includes Apply Changes beneath the language list. Waterllama marks its current choice with a check in a list of native names. An explicit Apply action can let the person inspect a choice before committing; immediate switching can reduce steps. The important requirement is that the interface consistently communicates which model it uses.

In an Apply model, distinguish the pending choice from the confirmed language and keep Cancel available if the editor behaves transactionally. Disable or clearly explain an unchanged Apply action. In an immediate model, update the selected state and visible interface together after the required resources are available. Avoid showing a confirmed check beside a language while the rest of the app remains unpredictably mixed.

A language switch can change word length, reading direction and text metrics. Keep the confirmation action reachable during the transition and restore focus to a sensible place. Do not dismiss the user into an unrelated home screen merely because rebuilding navigation is easier. Preserve unsent text and the current workflow, or explicitly explain any unavoidable restart before it occurs.

Explain what following the system means

Albo includes a selected System default option. Ask Agent shows System Language with English in parentheses and also offers a separate explicit English option. That distinction gives the person control over whether the app follows future device changes or stays in a chosen language. Two rows can currently produce English while representing different preferences.

Keep the preference mode separate from the resolved locale. System default means follow the operating system’s applicable language preference where supported. English means keep English even if that preference changes. Show the currently resolved language as supporting information rather than storing it as though the person explicitly selected it. Otherwise the app can stop following the system without telling them.

Define the fallback when a device language is unavailable. A short explanation such as Uses English when your device language is unsupported is more useful than a silent surprise. Do not reset an explicit user choice after an app update adds new translations. Test system changes while the app is open and after relaunch, including whether the platform already offers per-app language preferences.

Keep locale identity separate from translated labels

Store a stable supported locale identifier and a separate follow-system mode. Never use the translated display name as the database key. Translation updates, accents and regional naming can change the label without changing the preference. Resolve supported fallbacks centrally so settings, notifications and downloaded resources do not each invent a different language rule.

Load the resources needed for a switch before confirming success. If a network request fails, preserve the last complete usable interface and explain the retry. A partially translated screen can be worse than a clear unchanged state, especially if the person is trying to escape an unfamiliar language. Keep a reliable path back to the language setting even when optional remote content fails.

Test right-to-left layouts as layouts, not just strings. Navigation direction, alignment, mixed-script numbers, icons and clipped labels need deliberate review. Do not mirror meaningful media or every symbol indiscriminately. Also test larger accessibility text and script-specific font fallback. A picker that looks balanced in English may truncate the very native names needed for recovery.

Verify the whole task after the language changes

Ask testers to change language from an unfamiliar starting point, return to their previous task and reverse the choice. Include a region-specific option and System default. Check whether they can explain what changed and what did not. If people expect their learning target or transcript to change, the scope label needs work even if the switch itself succeeds.

Exercise missing translation keys, unavailable downloads, device-language changes and relaunch. Inspect permission dialogs, account emails and system-owned screens separately because the app may not control their language in the same way. Explain limitations without promising that one setting governs every external surface.

Review dates, decimal separators and long content with the changed locale. A display-format change must not reinterpret a saved amount or appointment. Preserve user-entered text exactly. Keep analytics on selection, application failure and reversal distinct: a quick reversal can signal a mistaken choice, but it is not by itself proof that the translation quality is poor.

Review language as a recoverable preference

Use these checks on a working build, not only on the polished reference state.

• ✓The label identifies interface language rather than leaving its scope implicit.
• ✓Native names remain visible without relying on flags.
• ✓Regional options correspond to genuinely supported differences.
• ✓The selected state and any pending state are distinguishable.
• ✓System-following mode remains separate from an explicit language.
• ✓Switching preserves drafts, progress and original user content.
• ✓Failed resource loading leaves a complete usable interface.

Keep language connected to settings and error recovery

The settings-screen examples show how a language preference fits into a wider settings hierarchy without becoming hard to find.

Use the mobile error-state examples to plan a clear recovery when a translation resource cannot be loaded.