doloc

What we like most about doloc is how little it asks of a development team. Instead of moving strings into a separate localization platform, it treats the repository as the source of truth and fits into the build or release step you already run. A single request sends the source and target files, and the updated target file comes straight back, ready to commit.

• Keeps existing translations, placeholders and file layout untouched while filling only what is missing
• Uses earlier translations as context, which helps product terminology stay consistent from release to release
• Works with common formats such as JSON, XLIFF, ARB, Android XML and Properties
• Ships with integration guides for Angular, React Intl, Flutter, Android, GitHub Actions and JetBrains IDEs
• Bills by unique source texts, so adding another target language does not raise your plan tier

doloc is best for small and mid-sized software teams where developers own the localization files and want routine UI copy translated automatically. The team is open that it is not built for translator assignments or approval workflows, so larger localization programs may still want a full platform. A practical tip: run doloc as a CI step on your main branch so new strings arrive translated in the same pull request, then spot check a few key screens with a native speaker before each release.