<!-- LLM_VERSION_INFO
FORMAT: text/markdown
CONTENT_TYPE: listing
ORIGINAL_URL: https://lingo.dev/en/guides
ALTERNATE_VERSION: en/guides/index.html (text/html)
EXTRACTION_DATE: 2026-04-18T22:16:57.622Z

This is the markdown version with text-only content (images converted to alt-text).
For rich formatting with images, request the HTML version at: en/guides/index.html
-->

# Localization Guides

Max Prilutskiy·Updated about 1 month ago·2 min read

Each guide walks through a specific localization scenario end-to-end - from configuring a localization engine on Lingo.dev to shipping translated output in production. Every guide assumes you have an organization and at least one localization engine configured.

## How Guides Work

Every product has different localization surfaces. A web app needs translated UI strings. An API needs localized responses. A documentation site needs translated Markdown files. Each surface connects to the same localization engine, but the integration pattern differs.

These guides cover seven integration patterns:

| Surface | What gets localized | Integration method |
| --- | --- | --- |
| [Translation API](/content/en/guides/translation-api/index.html) | Key-value data, dynamic content | HTTP API calls |
| [Web apps](/content/en/guides/web-app/index.html) | UI strings, component text | CLI + framework integration |
| [Mobile apps](/content/en/guides/mobile-app/index.html) | iOS `.strings`, Android `.xml` | CLI + mobile build pipeline |
| [iOS apps](/content/en/guides/ios-app-localization/index.html) | Xcode String Catalogs `.xcstrings` | CLI + GitHub Actions |
| [Android apps](/content/en/guides/android-app-localization/index.html) | Android `strings.xml` | CLI + GitHub Actions |
| [Emails](/content/en/guides/emails/index.html) | Transactional and marketing templates | API or CLI depending on template format |
| [Static content](/content/en/guides/static-content/index.html) | Markdown, JSON, YAML files | CLI with file-based translation |
| [CI/CD workflows](/content/en/guides/ci-cd-workflows/index.html) | All of the above, automated | GitHub Actions, GitLab CI, Bitbucket Pipelines |

### Prerequisites

All guides require an [API key](/content/en/docs/platform/api-keys/index.html) and a configured [localization engine](/content/en/docs/platform/engines/index.html). If you haven't set these up yet, start with the [documentation](/content/en/docs/platform/index.html).

## Choose Your Guide

[Translation API\n\nSend key-value data to the localization API and get translations back programmatically](/content/en/guides/translation-api/index.html)  
[Web App\n\nLocalize React, Next.js, and other web frameworks using the CLI](/content/en/guides/web-app/index.html)  
[Mobile App\n\nLocalize iOS and Android applications with per-locale model selection](/content/en/guides/mobile-app/index.html)  
[iOS with String Catalogs\n\nEnd-to-end Xcode .xcstrings localization with CLI and GitHub Actions](/content/en/guides/ios-app-localization/index.html)  
[Android with strings.xml\n\nEnd-to-end Android XML localization with CLI and GitHub Actions](/content/en/guides/android-app-localization/index.html)  
[Emails\n\nTranslate transactional and marketing email templates with brand voice applied](/content/en/guides/emails/index.html)  
[Static Content\n\nTranslate Markdown, JSON, and other static files in your repository](/content/en/guides/static-content/index.html)  
[CI/CD Workflows\n\nAutomate localization on every push with GitHub Actions, GitLab CI, or Bitbucket](/content/en/guides/ci-cd-workflows/index.html)  
[Engine Setup with MCP\n\nConfigure a localization engine using AI coding assistants through the Lingo.dev MCP server](/content/en/guides/mcp-engine-setup/index.html)  
[Jira Triage\n\nAutomatically triage Jira tickets for localization relevance with AI-powered suggestions](/content/en/guides/triage/index.html)