WebTranslateIt VS Lokalise

WebTranslateIt Reviews

1. Lizzie    

   Project Manager at Liveminds | over 1 year ago
   Great tool!

   We've used WebTranslateIt for years to translate our platforms, IOS & Andriod mobile apps into 30+ Languages. We've always used freelance translators and the process has always been so simple to get them set up and translating straight away which is so helpful, particularly on a tight deadline. The discussions feature has been invaluable to support translators in context to the appropriate string.

2. J Bonniot    

   Project Manager at Molotov | over 1 year ago
   Great Translation Project Management Service

   We use WebTranslateIt for the coordination of large translation projects for apps and websites : it's easy to use, easy to import translation files, easy to export, and easy to dialogue with different collaborators.

   👍 Pros:    Easy to use|Third party service integration|Auto translation|Project management

   👎 Cons:    Ui is not very attractive
3. Ines Karu    

   Product Owner of Fitekin at Unifiedpost AS | over 1 year ago
   Easy and simple

   It was very easy to implement the Webtranslatelt and import existing translation keys to Webtranslatelt using the APIs. Also, the translators' onboarding was quick and didn´t need much support.

   👍 Pros:    Quick and easy|Easy to setup|Intuitive|Unlimited users|User rights restrictions based on languages|Great customer support|Translation key comments are visible (no need extra clicks)

   👎 Cons:    Ui is not very attractive|Attached screenshots need to open in separate tab

Lokalise Reviews

WebTranslateIt mentions (1)

• free-for.dev

  Webtranslateit.com — Free up to 500 strings. - Source: dev.to / 7 months ago

Lokalise mentions (10)

• Localizations in Flutter

  Localise has no problem reading the json files or export to json, we recently started using it in collaboration with external translators. Source: about 1 month ago

• Why can't Apple fully translate their iOS interface into all supported languages?

  Actually I don't have "my" app. But in our app we use https://lokalise.com/ to localize it even to Norwegian. Our team is not the most expensive company in the world btw. And we don't have 1B+ users all over the world. Source: about 2 months ago

• Markdown, Asciidoc, or reStructuredText - a tale of docs-as-code

  Internationalization (i18n) pain for a documentation project is a process problem, not a feature gap. Documentation frameworks are not meant to translate your developer docs for you into the language of your choice. Some frameworks might offer i18n support, like the Crowdin support in Docusauraus v2. With Jekyll, you have to pick a theme like this one. I doubt if the reST or adoc frameworks would differ much from... - Source: dev.to / 5 months ago

• I made a site that enables super simple translation management and directly integrates with the Github repository

  I've been thinking about building a micro saas very similar to this after having so many issues coordinating the localization of several products I manage. The only robust options in the market are incredibly expensive (for example https://lokalise.com/). Source: 9 months ago

• We Put Half a Million Files in One Git Repository, Here’s What We Learned

  For the app I work at the moment we use https://lokalise.com/. We add translation strings to a SaaS app, and then the translation team translate them. I've written a build tool that downloads the translation JSON files from the API using the CLI, or as part of our CI process. Other teams have tools that download their language packs for different iOS and Android apps. The translations are versioned in Lokalise and... - Source: Hacker News / 12 months ago