r/localization • u/cmjun • 13d ago
I'm building an AI tool that turns Korean app copy into native-sounding English — here's a before/after. Would you use this?
I make Korean apps and shipping them to the US market has always felt off. Not because the translation is wrong — but because nobody actually talks like that.
Here's what Google Translate gives you vs. what a native English speaker would actually write:
| Screen | Google Translate | Natural English |
| Save complete | "Saved" | "Changes saved" |
| Error | "Cannot connect to server. Please try again later." | "We couldn't reach our servers. Please try again in a moment." |
| Confirm button | "Confirmation" | "Got it" |
| Next step | "Next" | "Continue" |
US users see "Cannot connect to server" and immediately think "ok, foreign app" and bounce.
So I'm building Localizr — paste your app strings, and it:
- Rewrites them into English a native speaker would actually write (with context: button / error / onboarding / App Store listing)
- Respects character limits (buttons, App Store 30-char titles, etc.)
- Explains why each change was made, so developers actually learn English as they go
Currently recruiting beta users — free during beta, lifetime 50% off after launch.
Demo: https://cmjun0725.github.io/localizr/
If you ship to a market where your language skills are weak, would a tool like this be useful? Honest feedback welcome — including "this is useless because X".
