LocalePilot reads and writes the files of fastlane deliver. You adapt your listing in every language with Apple's limits checked as you type, then publish with the tools you already use.
Real LocalePilot screens, captured on a demo project.
LocalePilot works in fastlane/metadata/<locale>/, at the project root, under ios/ or under macos/: name.txt, subtitle.txt, promotional_text.txt, description.txt and keywords.txt. Nothing is sent to Apple: fastlane deliver or App Store Connect remain your publishing tool.
The model is instructed to use only your source listing and not invent claims. Review every field before saving; publication remains in your usual tools.
Only changed fields are written, and a file changed on disk since it was loaded is never overwritten. Replaced files are backed up in LocalePilot's own storage on your Mac, never inside your project. Open them from Settings > Project > Backups > Show backups in Finder.
The App Store listing is part of Pro, also available during the 14-day trial.
No. It writes your fastlane/metadata files; publishing is done with fastlane deliver or in App Store Connect.
The App Store Connect reference sets the keywords limit at 100 bytes. LocalePilot applies that rule, the safest one: in UTF-8, accented letters and non-Latin characters take several bytes, so a 90-character field can exceed it.
Not yet: the screen covers name, subtitle, promotional text, description and keywords.
LocalePilot is being finalized. Leave your email to hear when it launches.