iOS App Localization Example

Demonstrates automated localization for iOS Xcode String Catalogs (.xcstrings) with the Lingo.dev CLI (@lingo.dev/cli) push/pull flow.

Full walkthrough: lingo.dev/en/guides/ios-app-localization

• MyApp/Localizable.xcstrings — String Catalog holding the source and every translated locale in one file
• .lingo/config.json — Lingo.dev CLI configuration

# 1. Install the CLI (or prefix commands with `npx`)
npm install -g @lingo.dev/cli

# 2. Authenticate and link this repo to your engine
lingo login
lingo link

# 3. Translate changed source into every locale
lingo push --wait

Every target locale is merged back into the same MyApp/Localizable.xcstrings — String Catalogs keep all languages in one file. This repo ships fully translated; after you edit the source strings, lingo push --wait translates only the delta. To bootstrap a brand-new locale, add it to .lingo/config.json and run lingo push --backfill-missing.

lingo push reads the String Catalog, diffs the source strings against .lingo/lock.json, and translates only new or changed entries through your linked engine. All target languages are written back into the same .xcstrings. Use lingo push --wait to block until results land, or run lingo push and lingo pull later to fetch them.

Want translations on every push or PR without running the CLI yourself? See the CI/CD Workflows guide — the Lingo.dev GitHub App translates automatically once installed. The App reads engineId from the committed .lingo/config.json, so run lingo link and commit the updated file before installing it.

• Source: en
• Targets: es, fr, de, ja

• Guide: iOS App Localization with Xcode String Catalogs
• Lingo.dev CLI docs
• Create a free account