---
title: Localize iOS and Android Apps in One Workflow | Smartcat
description: Translate Android strings.xml and iOS .strings in one project, with plurals, String Catalogs and pseudolocale testing. Try Smartcat free.
canonical: https://www.smartcat.com/guides/guide-localize-ios-and-android-apps/
language: en
updated: 2026-11-09
---

# Localize iOS and Android Apps in One Workflow | Smartcat

[Guides](https://www.smartcat.com/guides/) How to Localize iOS and Android Apps in One Workflow

[Maksym Ostapenko](https://www.smartcat.com/authors/maksym-ostapenko/) Head of Product Growth, Smartcat Updated November 1, 2026 · 7 min read

**AI summary**

The same app ships twice, once for Android and once for iOS, and each platform stores its text in a different file. Translating them separately doubles the work and lets the two apps drift apart, one button at a time.

Mobile app localization means adapting an app’s interface text, plurals and store copy for each language and market. The short answer: keep both platforms’ strings in one project with one translation memory, and export each native format. Smartcat does this for strings.xml and .strings files.

This guide covers choosing a tool, translating both platforms together, plurals, String Catalogs, cross-platform frameworks and testing. The examples use Smartcat.

Key takeaways

- **One project, two platforms.** Smartcat imports Android strings.xml and iOS .strings as keys and exports each native file.
- **Translate shared strings once.** One translation memory serves both apps.
- **Plurals per language.** English uses two plural categories, Arabic six; each form is its own segment.
- **String Catalogs work as files.** Smartcat translates .xcstrings and .stringsdict as file uploads.
- **Test before the store.** Android’s XA and XB pseudolocales and Xcode’s pseudolanguages expose layout bugs early.
What are the best tools to localize an iOS and Android app?

Look for one project that holds both platforms’ strings, shares a glossary and translation memory, and exports each file in its native format. Smartcat imports Android strings.xml and iOS .strings files as keys into one software localization project and translates them into any of 280+ languages.

| | What to check | Why it matters on mobile | In Smartcat

| Both native formats | Android and iOS store strings differently | Android XML and iOS .strings import and export as keys

| Plurals | Android and iOS .stringsdict differ | Plural segments in the editor; .stringsdict as a file upload

| Cross-platform reuse | The same button text on both apps | Shared translation memory and glossaries

| Repository sync | Strings change every sprint | GitHub, GitLab and Bitbucket integration, CLI, REST API

| Design stage | Text that doesn’t fit is cheaper to fix in Figma | Figma plugin with keys, variants and JSON export

| Review | Short labels are easy to mistranslate | AI translation plus your reviewers or Smartcat linguists

For a step-by-step walk through each platform, see the [Android app localization](https://www.smartcat.com/blog/android-app-localization/) and [iOS app localization](https://www.smartcat.com/blog/ios-app-localization/) guides on the blog.

How do you translate Android strings.xml and iOS .strings files in one project?

Import both files as key collections in the same Smartcat project, translate once, and export each platform’s file. One Smartcat project can hold several collections, so an Android app and an iOS app share one translation memory and 92% of AI-translated words need no human edit.

- **Create the project.** Choose the software localization project type, the source language and your target languages.
- **Import both platforms.** Push strings.xml and Localizable.strings through the CLI, the API or the Git integration ([Android](https://www.smartcat.com/integrations/git-android/), [iOS](https://www.smartcat.com/integrations/git-ios/)).
- **Translate and review.** AI translates with your glossary; strings shared by both apps are translated once and reused.
- **Export per platform.** Download or pull Android XML and iOS .strings for every language, ready for the app bundle. Creating an iOS app localization project with English as the source and Spanish and French as targets.
Welcome, %1$s!

%d unread message
%d unread messages

Translated: the text of each string and plural item. Locked: the name attributes, the quantity keywords and the %1$s and %d placeholders.
How do you handle plurals when you localize a mobile app?

Give every language the plural forms its grammar uses, not the two English has. Android’s resource accepts six quantity values, zero, one, two, few, many and other [(Android Developers: String resources)](https://developer.android.com/guide/topics/resources/string-resource), and Smartcat shows each form as its own segment so a translator can’t skip one.

- **Android:** each in strings.xml is a separate string to translate.
- **iOS .stringsdict:** Smartcat translates .stringsdict files as file uploads, alongside the .strings collection.
- **How many forms:** English uses two plural categories, Polish four and Arabic six [(Unicode CLDR: Language plural rules)](https://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html).
- **Zero is grammar, not a number:** Android ignores “zero” in English even when the count is 0, so write “No messages” as a separate string.
Can you translate Xcode String Catalogs (.xcstrings)?

Yes. String Catalogs arrived with Xcode 15 as a new file type that holds every language in one .xcstrings file [(Apple: Xcode 15 release notes)](https://developer.apple.com/documentation/xcode-release-notes/xcode-15-release-notes), and Smartcat translates .xcstrings files as file uploads, returning the same file with the new languages filled in.

- **Default file:** Xcode creates Localizable.xcstrings [(Apple: Localizing and varying text with a string catalog)](https://developer.apple.com/documentation/xcode/localizing-and-varying-text-with-a-string-catalog); upload it as a file, not as a key collection.
- **Older projects:** .strings files still import as keys, so mixed projects can use both.
- **Review in context:** the comments developers add in Xcode help translators pick the right meaning. **“We can reuse translations across sizes (square, rectangular) using the TM, so designers don’t rebuild every variant.” Magdalena Tumulka, Localization Lead, Huel How do you localize a React Native or Flutter app? React Native apps usually keep strings in i18next-style JSON, which imports into Smartcat as keys with placeholders and ICU plurals handled. Flutter’s ARB files aren’t on Smartcat’s supported format list, so confirm your workflow with a Smartcat specialist before you plan around it. Smartcat supports 80+ file formats in all. - React Native: import en.json, translate, export one JSON file per language ( JSON and YAML locale files ). - Shared copy: marketing screens and onboarding text often live in a CMS; keep them in the same Smartcat workspace so terminology matches the app. - Native modules: any Android or iOS string files in the project import as keys like a native app ( mobile app localization ). How do you test a localized app before it reaches the app stores? Run the app in a pseudolocale before translation, then check real translations on devices. Android ships two pseudolocales, English (XA) with accented, expanded text and AR (XB) with right-to-left text (Android Developers: Test your app with pseudolocales) ; Smartcat adds automated QA checks and reviewer approval before strings reach the build. - iOS: Xcode can run the app in a double-length or right-to-left pseudolanguage (Apple: Testing your internationalized app (archived guide)) . - Length: short English labels grow the most in translation, so test tab bars and buttons first. - Progress: Smartcat shows translation progress per language, so you know which locales are ready to ship. App localization progress per language in Smartcat. The full test plan, from pseudo-localization to linguistic QA, is in how to catch localization bugs before release . Try it on your app’s string files Import one strings.xml and one .strings file and export both in two new languages ( mobile app localization in Smartcat ). Book a demo Start free trial Frequently asked questions Can I translate Android and iOS strings in the same Smartcat project? Yes. Import Android XML and iOS .strings files as key collections in one project; strings both apps share are translated once, and each platform exports in its own format. Does Smartcat support iOS .stringsdict and .xcstrings files? Yes, as file uploads. Smartcat translates .stringsdict and .xcstrings files in file projects; .strings files import as keys in software localization projects. Does Smartcat support Flutter ARB files? Not today. ARB files aren’t on Smartcat’s supported format list, so confirm your workflow with a Smartcat specialist before you plan around it. React Native JSON files are supported. Can designers translate app screens in Figma first? Yes. Smartcat’s Figma plugin translates design text, handles keys and variants, and exports JSON ( Figma integration ). How do I add a new language to my app later? Add the language to the Smartcat project at any time; existing keys translate with the same glossary and memory, and only new and changed strings are billed. Is Smartcat affiliated with the companies named in this guide? No. Smartcat is an independent platform and is not affiliated with, endorsed by, sponsored by or otherwise associated with any company or product named in this guide. All product names and trademarks are the property of their respective owners and are used solely for identification and comparison. Related guides - How to translate JSON and YAML locale files Keys, placeholders and plurals intact. - How to catch localization bugs before release Pseudo-localization, linguistic QA and length limits. - How to keep software localization in sync with every release Git, CLI and API automation for SaaS teams. - Mobile app localization: everything developers need to know The developer’s view of app localization. - Software localization: the complete guide Formats, i18n, mobile, testing and developer workflows in one place. Sources - Android Developers: String resources - Android Developers: Test your app with pseudolocales - Apple: Xcode 15 release notes - Apple: Localizing and varying text with a string catalog - Apple: Testing your internationalized app (archived guide) - Unicode CLDR: Language plural rules Share this guide** [@](mailto:?subject=How%20to%20Localize%20iOS%20and%20Android%20Apps%20in%20One%20Workflow&body=https%3A%2F%2Fwww.smartcat.com%2Fguides%2Fguide-localize-ios-and-android-apps%2F)

[Maksym Ostapenko](https://www.smartcat.com/authors/maksym-ostapenko/) · Head of Product Growth, Smartcat

Maksym Ostapenko is Head of Product Growth at Smartcat, where he works on AI translation workflows, software localization and enterprise localization. He writes about translation technology and localization operations from hands-on product experience.

[LinkedIn](https://www.linkedin.com/in/maksymostapenko/)

GitHub, GitLab, Bitbucket, Figma, Android, iOS, Xcode, .NET and all other product names are trademarks of their respective owners. Smartcat is not affiliated with, endorsed by or sponsored by any company named in this guide; names are used solely for identification and comparison.
