Smartling is a translation no-brainer.
Use Cases and Deployment Scope
We use Smartling to help localize and translate strings. It lets designers, developers, and copywriters focus on the same language when creating features, then lets translators populate a string bank for other languages. This creates a much more streamlined approach to launching the feature and getting it in front of your customers faster.
Pros
- A searchable/filterable string bank that lets anyone find common strings that may already be translated and implement them in their project.
- A streamlined workflow for submitting new strings and files, allowing localization experts to translate them into more languages. You can then easily retrieve these translations and implement them in your project once they're complete.
- Connected to today's workflows, from MCPs to APIs, so you can sync your apps, SDKs, and more to streamline strings into your project in real time.
Cons
- The UI can feel intimidating and clunky at first. Maybe we can spend some resources simplifying this by letting users start different workflows from a landing page.
- The UI can feel dated at times. Sometimes I forget to select projects, and they can get lost among the many other options you have to check off to ensure everything is set up correctly for the task at hand.
Return on Investment
- We can think in English and know that Smartling can localize and translate for the rest of the world's markets. This probably would have taken weeks, or at least a month, before Smartling, and now we can have translated strings for 150+ markets in a matter of a week.
