We've talked to founders, developers, and localization teams over the last few months, and one thing kept coming up: translation quality keeps getting better, but products still feel different across languages.
We're curious how others are handling this today.
Have you ever reviewed a translation that was technically correct but just didn't sound like your product anymore?
LocIn AI
CI validation sounds useful, but I’m curious how far it goes. If a translation changes a placeholder like {{count}} or {{planName}}, does LocIn fail the check, or is validate mostly checking missing keys and basic file structure?
LocIn AI
@novamaker01 It goes quite a bit further than basic validation. It'll catch things like missing keys, broken file structure and yes placeholder mismatches which will fail the check like you suggested. It also checks for untranslated content, makes sure HTML tags like <strong> or <br> are preserved, and warns about suspicious cases like where a translation is dramatically longer or shorter than the source. We also support things like the --min-coverage flag if you want to enforce a minimum translation coverage in CI. If you're curious, the docs are linked on our landing page. And if you end up trying it out, feel free to reach out with feedback or feature requests. We'd genuinely love to hear what would make it fit better into your workflow
"Tone-aware" is the part most localization tools quietly skip. I'm Italian shipping apps in English, so I feel it both ways... the words come out right but the register is off, too formal or oddly casual for the screen it sits on. And a two-word button has no sentence around it to infer tone from, which is where machine translation usually guesses wrong. What's it keying off for tone when the context is that thin?
LocIn AI
@luca_capone That's exactly the kind of problem that got us interested in this space in the first place.
When the context is thin, we lean heavily on the tone profile, glossary, and the rest of the project content to build a better understanding of how the product communicates. A two-word button on its own is tough for any system, but it becomes a lot easier when it's translated as part of a larger product instead of as an isolated string.
We're definitely not claiming to solve context perfectly every time, but we've found that giving the model a stronger understanding of the product itself gets much better results than treating every string independently.
Who reviews the output? Shipping AI translations straight to production without a human-in-the-loop step sounds risky for anything customer-facing. Is there a review workflow or glossary/term base supportt?
LocIn AI
@ahmeterdempmk We definitely agree that blindly shipping AI-generated translations to production can be risky. That's why we have multiple review and validation layers that check translations, flag potential issues, and in some cases recommend manual review when confidence is low. We also support things like glossaries and terminology rules so teams can enforce consistency across languages. Our goal isn't to remove humans from the loop entirely, it's to dramatically reduce the amount of manual work while still keeping quality high.
The developer workflow is the strongest part for me. Localization usually becomes a messy spreadsheet process after the first few languages, so having CLI/API support from the start makes this feel much easier to maintain.
LocIn AI
@farrukh_butt1 absolutely right. at some point every localization workflow seems to turn into "wait, where is the latest version of this file?" 😅 we're basically trying to make sure people never end up there in the first place
Tone-aware localization addresses the part that generic translation APIs get wrong. Most tools produce technically correct strings that sound robotic in the target language because they ignore register and brand voice. How does the tone model handle language pairs where formality rules are structurally different, like Japanese honorific levels or the tu/vous distinction in French?
Stripo.email
Congratulations on the launch! 🎉 Localization is one of those problems that seems solved until you actually try to maintain a consistent brand voice across multiple languages.
LocIn AI
@marianna_tymchuk Thank you! That's exactly what we kept running into. Getting a translation is easy now, but getting it to sound like the same product is a completely different challenge. Really appreciate the support 🚀