Hero image for Localization

Localization is implemented in all project regardless of the number of supported languages. Thus, adding an extra language won’t cause any difficulty in the future.


Creating and maintaining translations can be a very tedious and manual process, think spreadsheets nightmares 😱. In addition, external stakeholders usually have the responsibility of translating the content from English to other languages. Therefore, we prefer using third party services like Phrase to manage localization strings.

The process usually involves the following steps:

  1. Developers - us - pushes new localization keys or remove deprecated keys.
  2. External stakeholders - the client - translate the content.
  3. Developers - us - pulls the translated content into the project. This step often happens at build time (mobile application) or upon deployment (web application).

The process to push/pull localization keys is done via a CLI tool. It’s important to automate this process as much as possible.