Accelerate your Android app translation workflow

Pick a workflow that reads your string resources directly instead of copy-pasted text, syncs with your Git repository, handles plural forms and keeps a glossary.

It should also let a human reviewer check strings before release. Smartcat fits teams that ship updates often and want repository sync, AI translation and review in one workspace.

Smartcat has no free-forever plan, but the trial is free: 15,000 Smartwords over 15 days, with no credit card. API access is included in the trial.

That is usually enough to translate the strings of a small app into a few languages and judge the output before you buy.

• Connect your Git repository, or upload the Android XML file.
• Choose your target languages.
• Let AI translate the strings with your glossary and translation memory.
• Review them in the editor, alone or with a linguist.
• Push the translated files back to the repository or download them.

In 2026, 92% of words translated by Smartcat AI for paying customers were accepted without a single human edit.

App strings are short, so a word like "Save" or "Home" can be ambiguous. Attach screenshots for context and have a reviewer check key screens before release.

Smartcat is SOC 2 Type II compliant. Content is encrypted in transit and at rest, and role-based access limits who can open each project.

Translators work in the editor, so they never see your repository. On written request, your content is deleted or returned within 30 days.

Common options are editing strings yourself in Android Studio, sending files to freelancers or an agency, or another translation management system.

One honest limitation: Smartcat translates your string resources, not the running app. Test the localized build on devices to catch text that overflows a button or layout.

Smartcat reads Android XML string resources, and also JSON, YAML, XLIFF 1.2 and 2.0, PO, RESX and Java PROPERTIES files.

In a software localization project you can import keys from Android XML and export them back to Android XML. The Help Center lists all 80+ supported formats.

Yes. Plurals can be handled natively, as separate segments in the editor, or through ICU MessageFormat syntax.

When you add a new key in the editor, you choose whether to create it with all plural forms. On export, plural forms are converted into an ICU MessageFormat-compatible string.

Yes. The Git integration can push translations back when they are complete or when they reach a workflow stage you choose.

Teams with a hybrid workflow often push AI-translated strings early for internal testing, then let the reviewed version overwrite them once a linguist confirms each segment.

Upload screenshots or add context notes to segments directly in the editor, so the translator sees where a string appears.

If you import keys as LocJSON, you can also pass comments and a maximum string length for each unit, which helps linguists keep labels short enough for buttons.

Yes. When you import keys into a software localization project, you can upload both the source strings and existing translations for each language.

If a key already exists in Smartcat with a different value, choose Skip to keep the Smartcat value or Overwrite to replace it with the one from your file.

Yes. Put the title, short and full descriptions and release notes in a spreadsheet or document, upload it, and translate it into every store language.

Use the same glossary as the app, so feature names match between the listing and the screens users see after they install.