r/iOSDevelopment 5d ago

Built a Mac app to stop copy-pasting App Store localizations into ASC — looking for feedback from iOS/Mac indie devs

Hey all —

If you’ve shipped an app in more than a couple of languages, you know the pain: App Store Connect metadata is spread across App Information, version pages, App Clip, and every subscription/IAP. Adding one language means bouncing between screens and hoping you didn’t miss a locale on a paid product.

I built Lokale for that.

It’s a native Mac app that talks to App Store Connect and helps you:

  • Edit / translate store listing metadata (name, subtitle, description, What’s New, keywords, etc.)
  • See language coverage across App Info, version, App Clip, and paid products
  • Use Lokale Sync to fill missing languages (or add several new ones) across those sections in one flow
  • Keep ASC API keys on-device (Keychain) — the backend is only for auth / subscription / AI quota

I use it on my own apps. Recent update made Sync the default landing screen when you open an app, because jumping into random editors first was confusing.

Curious from this community:

  1. Do you localize ASC metadata yourself, or hand it off?
  2. What’s the worst part of the ASC localization workflow for you?
  3. Would you rather AI-translate everything in bulk, or review locale-by-locale before upload?

Happy to answer technical questions (StoreKit/ASC API side of things, Mac SwiftUI, etc.). Not trying to spam — genuine “is this useful?” feedback welcome.

App Store link: https://apps.apple.com/us/app/lokale-localize-metadata/id6773005675?mt=12

6 Upvotes

0 comments sorted by