Wispr Flow: Dictation That Works EverywhereStop typing. Start speaking. 4x faster.
Promoted
AppUFO
Ship localised Apps faster
64 followers
Ship localised Apps faster
64 followers
Reach more users worldwide without spending days or hundreds on app localisation. Localise your Xcode projects in minutes, reduce translation costs, and spend less time managing strings so you can focus on building great apps.
TinyFast
congrats on the launch, localisation is exactly the kind of chore that eats a weekend right before you want to ship. one thing I'm curious about beyond the plural rules question already asked - the same source string sometimes needs different translations depending on context, like "Save" as a button vs "Save" as a noun in a settings label. does AppUFO give translators any way to see or add context for a string (comments, screenshot, surrounding key names), or is it working off the raw string key alone?
TinyFast
TinyFast
localisation is one of those things that always takes way longer than it should, so this is a welcome idea. curious how it handles plural rules and gendered strings though - languages like Arabic or Polish have way more plural forms than English, and that's usually where automated localisation tools fall apart and produce grammatically broken UI text. does AppUFO handle that at the ICU/stringsdict level or is it more of a straight string-for-string translation?
TinyFast
The App Store context pull is a smart move — working off bare string keys is where most localisation tools produce plausible-but-wrong translations. One thing I would want to check before wiring this into a CI pipeline: does AppUFO support the .xcstrings (String Catalog) format that Xcode 15 introduced, or is it still expecting the older .strings and .stringsdict files? That migration path is usually where these tools either save or cost extra time on existing projects.
TinyFast
That's the answer I was hoping for — drop-in support means zero migration friction. One quick follow-up: does AppUFO read the sourceLanguage declared in the .xcstrings file itself, or does it require you to set the source language separately in the tool?
Pulling context straight from the App Store listing instead of asking translators to work off bare keys is a smart shortcut - didn't realize it went that route. That should cut down a lot of the ambiguous cases without needing a whole review workflow.
TinyFast
I'm wondering if you've seen an increase in users from new markets after localizing with your tool.
TinyFast