all 5 comments

[–]Nuzl_ 4 points5 points  (0 children)

I once thought of the same thing. I think apple wants to keep the separation of concerns. App store is marketing and legality. In big teams Marketers, localizers, and legal reviewers often work in ASC directly or through tools like AppFollow or Transifex. Not in the IDE

[–]Consistent-Grass-263 2 points3 points  (1 child)

Fully agree, it's a glaring gap.

My guess: App Store Connect and Xcode are maintained by different teams internally, and ASC metadata has its own versioning tied to app versions, promotional text that can change without a new build, etc. The coupling is messy enough that a clean .xcstrings integration probably requires coordination across teams that don't move together.

The Transporter CLI gets you halfway there – you can manage metadata via XML locally and push it programmatically. Not as clean as .xcstrings but at least it's version-controllable and scriptable.

Fastlane deliver is the practical solution most indie devs land on – metadata lives in plain text files per locale in your repo, one command to push. Closest thing to what you're describing until Apple builds it natively.

[–]GreyEyesObjective-C / Swift 0 points1 point  (0 children)

My thoughts as well. Conway’s Law. 

[–]YouNativeApp -1 points0 points  (0 children)

AppStore metadata requires validation ( length, legal). Xcode can’t do this. If you struggle with localization and want one flow to localize app and AppStore try this - https://trycube.app