Localize an iOS app with code-aware CLI agents, .xcstrings and separate App Store copy files
An iOS developer describes using Claude Code to find missing strings and Codex CLI to translate .xcstrings, store metadata and screenshot text. App Store entry and screenshot layout remain manual.
Evidence: The author reports this. We have not checked it beyond reading the source.
The business problem
An app release needs consistent translations across interface strings, store listings and screenshots.
What was tried
Use .xcstrings rather than legacy .strings. The author first has Claude Code find strings Xcode missed, then uses multiple Codex CLI sessions for translations. For store copy, create aso_en.txt with English title, subtitle, keywords and description; ask the CLI for language files in that folder. Paste them into App Store Connect. Paste translated screenshot text into an editor and align it manually.
What was reported (positive)
u/LingonberryBoth613 reports three projects localized into seven new languages over a few days, with passes taking 10–30 minutes. No sales or translation-quality measurements supplied.
Limitations
Self-reported timings. Another commenter reports translation errors despite context and reviews. The author initially cross-checked with DeepL, then stopped. No independent validation or reusable script supplied.
What you need
iOS project access, .xcstrings, CLI agents and an editor for screenshots.
Sources
- u/LingonberryBoth613 on r/iosdev, including author replies ↗ Community discussion, publication date unknown
Source published: unknown. Last reviewed here: October 26, 2026. Spot a mistake? Tell us.
Tools in this workflow
- Claude Code: Finds strings omitted by Xcode extractionTry Claude Code
- Codex CLI: Translates app strings and store copyTry Codex CLI
- App Store Connect: Receives manually pasted localized listingsTry App Store Connect
Get new workflows like this by email
A short selection of the most useful new workflows, including the ones that did not work. Free, and you can unsubscribe at any time.
Related workflows
A Claude-built support inbox that drafts replies, pulls orders and learns from the owner's edits
A small online seller had Claude build Relay, an internal web app that turns email, Facebook and Instagram messages into tickets every 10 minutes, drafts replies with order data, and handles cancellations and returns after his approval.
A third AI model audits the code before launch: 100 bugs found in a no-code founder's SaaS
A founder with no coding skills builds with two AI models and points a third at the codebase only to audit, before taking payments. It found about 100 bugs, including broken payment credits, then became a standing check.
Write AI test specifications before implementation, or hide the function body from a fresh test-writing chat
A small-SaaS developer reports a double-refund bug despite passing AI-generated tests. Their revised Claude Code routine separates test specifications from implementation and uses a fresh chat for diff review.
Automate monthly refreshes of data-driven articles with an agent that fetches, filters, rebuilds and drafts for human review
An Ahrefs marketer describes a monthly pipeline that pulls fresh keyword data, filters it with written rules and examples, rebuilds tables, updates WordPress drafts and notifies the editor, who approves every change before it goes live.