This is the essential resource for developers, engineers, and technical leads. Content focuses on implementation, integration, and code-level best practices. Find step-by-step tutorials on connecting Lokalise to your CI/CD pipeline (GitHub Actions, GitLab), managing translation keys, and utilizing our SDKs and APIs for automation. The goal is to eliminate developer toil and achieve true continuous localization.
Today we will continue covering back-end frameworks and talk about localization of Phoenix applications with the help of Gettext. You might not have heard about Phoenix before, so let me say a couple of words about it. This is a server-side MVC framework written in Elixir, which is a functional programming language
Can you manage your iOS app's metadata in iTunes Connect? It's trickier than you think. Metadata are sections about your app: name, description and what’s new. At first, managing metadata is easy: you update one text file and copy its contents into iTunes. But time goes by and your app grows. You support more markets and localize into more languages. You n
“How do I integrate Lokalise into my deployment process?” All your answers are here, in one place. Bookmark this page for handy links to the latest list of Lokalise integration tools.
That's a common situation when you are developing your app for two and more platforms - say, iOS and Android, and some key names and values are the same and some are different. Lokalise can help you to avoid double translation work and stay clean in general by automatically merging these keys. One of the unique features of Lokalise is the ability to have key names exported differently depending on the platform. Coding for different platforms usual
Behind the scenes of localization with one of Europe’s leading digital health providers
Read more Case studies
Localization workflow for your web and mobile apps, games and digital content.
©2017-2026
All Rights Reserved.
