توطين نصوص الواجهة المشتركة

To reach the world, your UI text must adapt to each user. Localization serves the right language from your shared resources. 🌍

Localization builds on the shared strings you already defined. You keep the same keys but add translations for each language.

You add a values folder tagged with a language code, like values-es for Spanish. Each holds the same keys, translated.

The key welcome exists in every folder. Only the value changes, so your code never has to know the language.

The plain values folder is your fallback. If a translation is missing, Compose shows this default text instead of crashing.

Your screen still calls stringResource with the same key. The right language is picked automatically at runtime.

Compose checks the device locale and selects the matching folder. Spanish devices get values-es, others get the default.

One item versus many needs different wording. A plural resource lets each language choose the correct form for a count.

Word order differs by language. Use placeholders so each translation arranges values naturally for its grammar.

Switch the device or emulator language and rerun. Seeing real translations early catches layout and length surprises. ✅

Because translations live in shared resources, both apps localize from the same files. Add a language once, ship it everywhere. 🙂

You added locale folders, kept the same keys, and let Compose pick the language automatically. One codebase, many locales. 🌐