Google Cloud Translation API vs. Transifex

Transifex is great for when you have content you intend to 1) localize to multiple languages and 2) keep updated over time. It's probably not necessary for one-off projects that you expect to stand the test of time. It's also ideal for companies that intend to add more and more languages over time as business expands

Incentivized

• Integrates with other tools - makes localizing more straightforward and less of a gargantuan project.
• Easy to add a new language to a project - When making the business decision to expand languages, we can provide decision-makers with accurate estimates before committing to a new language.
• Provides access to multiple translation companies - We get to evaluate and pick the 3rd party translators that work best for our use case.

Incentivized

• Once you have a lot of resources in a project, ordering gets tricky because there's one long list of resources. I wish I could search for the resource when ordering.
• When you import your resources from another source, it will overwrite any changes you made to the translated article. For example, we stopped creating localized screenshots in our documentation because the images would be overwritten with the original English ones anytime we made updates.

Incentivized

Support has always been easy and fast. Anytime something has come up, we have gotten a quick response and had our issue resolved. Bugs don't seem to stick around for very long either. Seems like their Customer Success and Support groups are in great sync with each other, which always has a positive impact on the customer experience

Incentivized

• Fewer people needed - without Transifex, we would probably have to hire more staff to many just the localization projects.
• Meet business demand quickly - now that we are set up with our Transifex flow, adding a new language is relatively easy and we know exactly when to expect the final product to deliver to customers.

Incentivized