Strings: translate the text inside your product, release after release

The problem it's for

Your product text lives in string files: JSON, PO and friends. Every release adds a few keys and changes a few more. Somebody exports them, somebody translates them, somebody pastes them back, and nobody is quite sure which translations were actually reviewed.

Strings is meant to take that loop off your team: new and changed keys will go to Taia, translations will come back, and only approved text will reach your build.

What we're building

This is the plan for early access. Details can still change as we test it, and we'll tell you what is and isn't ready when we invite you.

• Keys, not files. Every piece of text is a key with a translation per language, tracked over time. Change the English and the other languages will know they need an update.
• Your repo and your CI. A command line tool will push new and changed strings to Taia and pull approved translations back, from your terminal or your CI pipeline.
• Common string file formats. We are working on JSON, PO, iOS and Android string files.
• AI translation that knows your terms. Your translation memory, glossary and style guide will go into every translation.
• An approval step. Only approved text will be served to your build, so an unreviewed draft never ships by accident.
• Linguists when you want them. A professional linguist will be able to review the strings that matter most, in the same editor.

How it's different

• ✓
  Documents and app text in one account. Your manuals and your app text will share one translation memory and one glossary, so a term is translated the same way everywhere. Audio and video are coming too.
• ✓
  Professional linguists are optional, not a second vendor. They work inside Taia, on the same projects. Our process is ISO 17100 certified.
• ✓
  Your content stays yours. Customer content is never used to train AI models.