Reviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
718 reviews
from
External reviews are not included in the AWS star rating for the product.
Powefull translation and versioning tool
What do you like best about the product?
The availability to add screenshots and to plug 3rd parties extensions. It is really easy to use and intuitive. There is no need for lenghtly trainings.
What do you dislike about the product?
User management and comment management could be improved.
What problems is the product solving and how is that benefiting you?
It is allowing different teams and market to localise content easily and with context. With the google translate feature we can do a 1st round of translation which make copywritter's life easier .
Excellent product for localization
What do you like best about the product?
I like that lokalise is easy to use for developers as well as for translations. I often have to use their search and it works great. Adding and editing new keys is easy.
Also, they have excellent customer service that is available all the time. All my issues that I've had have always been resolved quickly and efficiently
Also, they have excellent customer service that is available all the time. All my issues that I've had have always been resolved quickly and efficiently
What do you dislike about the product?
I cannot think of anything that I don't like
What problems is the product solving and how is that benefiting you?
We can lokalise our product very easily. Adding new languages is also easy and simple
Great product to speed up many business processes
What do you like best about the product?
Single source of truth as far as the copy is concerned, single point of access for all people dealing with the text (designers, translators, developers). Great customer support too!
What do you dislike about the product?
Perhaps too much focus on artificial intelligence and integration with figma still somewhat precarious
What problems is the product solving and how is that benefiting you?
I no longer have to go crazy with copy/paste to request translations, manually check the glossary, maintain a translation history, try to maintain consistency between different products
Efficient and easy to use
What do you like best about the product?
We can get keys translated into multiple languages and problems are generally dealt with very quickly.
What do you dislike about the product?
Translating keys in house that include HTML and/or placeholders can be difficult and throw up a lot of errors.
What problems is the product solving and how is that benefiting you?
It is helping us to translate into multiple languages, especially those for which we don't have in house translators.
Exceptional Support and Cutting-Edge Solutions
What do you like best about the product?
Their support team is incredibly responsive and always goes the extra mile to address any questions or challenges we’ve encountered.
What do you dislike about the product?
Honestly, there’s nothing I dislike about Lokaise.
What problems is the product solving and how is that benefiting you?
Their AI-powered translation tools and smooth integration options take the hassle out of traditional localization processes.
Lokalise is the perfect fit for our organization
What do you like best about the product?
It's intuitive and easy to use which makes onboarding our external translators and internal team members super efficient. Several integrations and automations are available. LokaliseAI is easy to implement and integrate into our workflows. Customer Support is fast, reliable and knowledgeable.
What do you dislike about the product?
Some of the integrations have limitations preventing us from fully taking advantage of them (ex. Braze, Figma). Using the APIs to integrate tools should be made easier. I wish Lokalise had a robust localization workflow portal (i.e. ticketing system) which allowed teams to submit translation requests and track them in a single place, for all projects.
What problems is the product solving and how is that benefiting you?
Lokalise allows us to manage and perform translation and localization-related tasks in a centralized place.
Lokalise for AI
What do you like best about the product?
My team and I appreciate the flexibilty available in Lokalise's platform. The ability to use a unified glossary and style guide amongst our projects, paired with Lokalise AI for translation, has been a powerful combination for us. We save time and have constantly updated translations.
We found Lokalise very easy to implement, using the out-of-the-box Zendesk integration. It's ideal to have our content constantly synced from Zendesk to Lokalise, so it's ready to be translated with daily updates.
We found Lokalise very easy to implement, using the out-of-the-box Zendesk integration. It's ideal to have our content constantly synced from Zendesk to Lokalise, so it's ready to be translated with daily updates.
What do you dislike about the product?
I've had issues with filter logic not working well in my instance. It's a bug that I'm hoping will be resolved, as otherwise the functionality is there!
What problems is the product solving and how is that benefiting you?
Lokalise was able to replace two different translation services for us, providing a variety of different contexts for translation.
Best translation management tool out there
What do you like best about the product?
I like the simplicity of use and the different CLI/integrations that make the tool usable not only in the web app but also in CI/CD environments
What do you dislike about the product?
Android/iOS integration is not so perfect, especially iOS ones with strings catalog
What problems is the product solving and how is that benefiting you?
Managing translations for Android and iOS apps
An invaluable tool in FE internationalisation
What do you like best about the product?
Lokalise makes an extremely tedious task such as internationalisation actually enjoyable to implement as a developer. Furthermore the end users have an easy time of understanding the UI, when they are managing their translations.
I am working with Lokalise on a daily basis both as a developer but also as support for our Marketing department. For all of our frontend solutions (Next.js, React.js and React Native) we are utilizing Lokalise for internationalization in three different ways:
For our Next.js website, Lokalise is connected via a webhook that I have set up for every domain. This means that any changes made by our franchise users are shown on the website in about 10 seconds. The integration of the webhook and connection to the Next.js API worked flawlessly and was very easy to do. Furthermore, the use of the useTranslation() hook makes it extremely easy to use the translations in your code on a day2day basic.
For our React.js integration we are mostly using Lokalise for storing all of our text content (everything is in English here). At one point we expect to do a proper localization of this application and I am sure that Lokalise will make it just as easy for us. One thing that we do not have in the client-side React.js app is the use of server-side API routes to trigger via the webhook and update the stored translations. I am excited to see how we will solve this challenge other than rebuilding and redeploying the project.
In the React Native application we are currently utilizing App Center to trigger a small in-app update for the users whenever a translation is changed.
I am working with Lokalise on a daily basis both as a developer but also as support for our Marketing department. For all of our frontend solutions (Next.js, React.js and React Native) we are utilizing Lokalise for internationalization in three different ways:
For our Next.js website, Lokalise is connected via a webhook that I have set up for every domain. This means that any changes made by our franchise users are shown on the website in about 10 seconds. The integration of the webhook and connection to the Next.js API worked flawlessly and was very easy to do. Furthermore, the use of the useTranslation() hook makes it extremely easy to use the translations in your code on a day2day basic.
For our React.js integration we are mostly using Lokalise for storing all of our text content (everything is in English here). At one point we expect to do a proper localization of this application and I am sure that Lokalise will make it just as easy for us. One thing that we do not have in the client-side React.js app is the use of server-side API routes to trigger via the webhook and update the stored translations. I am excited to see how we will solve this challenge other than rebuilding and redeploying the project.
In the React Native application we are currently utilizing App Center to trigger a small in-app update for the users whenever a translation is changed.
What do you dislike about the product?
For our franchise solution we need to have different variants of e.g. the english texts. While this can be solved on the web with our headless CMS solution it is not as intuitive in our app, where we have to rely on creating multiple sub-versions of every locale in Lokalise. This means that the multilangual view can get cluttered very quickly.
Some of the franchise users also have a hard time understanding the use of {{brackets}} for dynamic variables in the text, which sometimes causes UI bugs until it is noticed - maybe this could be done in a more user friendly way?
Some of the franchise users also have a hard time understanding the use of {{brackets}} for dynamic variables in the text, which sometimes causes UI bugs until it is noticed - maybe this could be done in a more user friendly way?
What problems is the product solving and how is that benefiting you?
Lokalise makes it viable and actually possible for our team to manage a cross-country franchise solition across different FE stacks. The integration capabilities, particularly the webhook setup for our Next.js website, enable us to reflect user-generated changes on our website in near real-time. This ensures our content is always current - a core requirement from our franchise customers. Although handling dynamic variables with {{brackets}} can be challenging, Lokalise provides the structure needed to manage this aspect, allowing for the use of personalized and context-sensitive content. Lokalise is a core part of our web facing setup.
Best software to date to start with localization
What do you like best about the product?
It's a very easy to learn/use tool. We currently implemented a Figma-to-Lokalise kind of workflow and once we set up the process right (this took a little bit of time haha), now things are running smoothly.
What do you dislike about the product?
The Figma plugin feels like it's in a very early stages of development. It works great in best case scenarios but there are a lot of unhappy paths that are not considered yet. We'd love to provide a few feature requests to make our life easier :)
What problems is the product solving and how is that benefiting you?
Creation, update and management of keys is the main value proposition. As well, an easy access for translation agencies helps a lot.
showing 91 - 100