App Store metadata, localized.
Every locale, in minutes.
Your customers search the App Store in their own language. AppMetadataLocalization pulls your listing out of App Store Connect, translates every field with the AI provider you choose, and publishes it back once you approve it.
Requires macOS 14 or later, an App Store Connect API key, and your own API key for Anthropic, OpenAI or DeepSeek. Listed on the Mac App Store as Appro: App Store Localization.
How it works
Connect and fetch
Sign in with an App Store Connect API key. The app lists your apps and pulls the localizations you already have, so your live listing is the source and nothing is invented from scratch.
Generate with your own AI
Bring your own key for Anthropic, OpenAI or DeepSeek. Choose the provider and model per run, or mix providers across locales. You pay the provider directly, at cost.
Review, then publish
Every locale opens beside your source metadata for inline editing and per-locale approval. Nothing reaches App Store Connect until you approve it.
What you get
- Every metadata field
- Name, subtitle, description, keywords, promotional text and release notes, generated for each locale you select.
- Apple limits, enforced
- Generation respects the real field limits, including the 100-byte keyword rule that quietly truncates Chinese, Japanese, Korean and Arabic listings.
- Finished locales left alone
- Locales that already have content in App Store Connect are skipped by default. Regenerating one is an explicit opt-in, so a translation you have already polished is never overwritten by accident.
- Failures retry alone
- A locale that fails retries on its own. One bad response never costs you the whole run, and never forces you to start over.
- Your keys, your provider
- API keys live in the macOS Keychain, never on disk in plaintext. There is no markup and no middleman: your AI provider bills you directly.
- No servers
- The app talks straight to Apple and to your AI provider. Your metadata never touches our infrastructure, because there is none.
Common questions
What do I need to get started?
An App Store Connect API key with the App Manager role, and an API key from at least one supported AI provider: Anthropic, OpenAI or DeepSeek. You enter both once and they are stored in the macOS Keychain.
Where do my API keys go?
Into the macOS Keychain, never to disk in plaintext and never to us. The app has no servers and no accounts. It talks directly to App Store Connect and to the AI provider you chose.
Which AI providers are supported?
Anthropic, OpenAI and DeepSeek. You pick the provider and model for each generation run, and you can mix providers across locales. The provider bills you directly at their own prices.
Will it overwrite metadata I already translated?
No. Locales that already have content in App Store Connect are skipped by default. Regenerating one is an explicit opt-in, and no locale is published until you approve it.
Can I edit what the AI writes?
Yes. Every locale opens side by side with your source metadata for inline editing. You approve each locale yourself, and only approved locales are published.
Does everything publish straight away?
Promotional text can be updated without a new submission. Every other field needs an app version in an editable state, exactly as Apple requires. The app checks the version state before publishing and reports the result for each locale.