Integrate POT

with Localazy within minutes.

Worried about your source code? Don’t be. All your source code remains only on your machine. The only thing uploaded to Localazy are the strings to be translated.

Localazy Android Library is optional. It brings your app a lot of benefits, but we also understand that maybe you are not happy to integrate 3rd party libraries into your app.

Hence, you can just use our CLI without Localazy Android library.

It may take up to 15-30 minutes to publish changes and replicate them to all our servers. Also, be sure to clean your project as we use intensive caching to speed up building your app and reduce the data transfers for the end-users.

The plugin indeed changes the bytecode of your app in several places. It looks for certain patterns to identify where the changes are needed. However, it never sends your source code nor the bytecode to anywhere and all changes are made strictly to inject the OTA feature.

Honestly, any plugin you add to your project can access your source code, resources and bytecode and our plugin is no different from Firebase or Google Services in term how it changes your bytecode.

We are ready to sign a contract binding us to not send your source code, resources or bytecode anywhere and inject only code strictly needed for OTA features.

The second option is to use our CLI, but you will lose the comfort of the automatic resolution of your project structure and OTA updates.

You can translate JSON files with the assitance of machine translation engines (such as Google Translator) and copy-pasting the results into your text editor. But this process is time-consuming and inefficient.

The easiest way on how to translate JSON file is to use an online service, such as Localazy. This way, you can translate multilingual JSON files, JSON5 files or HJSON files and seamlessly integrate translation management system into your workflow. To translate JSON files using the Localazy interface, sign up for free and create a new translation project. Once you upload your JSON file add a new language and start translating! You can even pre-translate the whole JSON file by applying machine translations in bulk.

Localazy is a state-of-the-art translation management platform and localization suite to help you translate your JSON files effectively. Learn more in the Getting Started Guide.

Yes, translations are downloaded to their original locations.

Phrases limit works over all of the apps under your account. You can increase the limit with a one-time payment and increase your limit forever. You will be informed in advance when you are close to the limit.

There is no hard limit at the moment, but it’s recommended to keep the size of each individual item under 4kB. This corresponds to 4,000 characters encoded as UTF-8 and 2,000 characters encoded as UTF-16. Uploading longer texts won’t yield any errors, but might get refused by some external translation engines integrated in Localazy.

We do not offer refunds. Please read Terms & Conditions of Localazy before purchase.

**In Localazy, every key can be in different states, which makes it invisible from the translation process. **

• Hidden: Hidden keys are not available to translators, but other than that, they are processed the same way as all the others. They are also exported in the output file.

Keys are automatically marked hidden under certain circumstances - when the source language translation is empty or when they are linked to another one using our ((Duplicate linking)) feature.

• Deprecated: Deprecated keys are invisible in the translation process and are not exported in the output file. Under certain circumstances, they can be exported for our Android/iOS SDK when the update is required from the older version of the app. If the key reappears in the input data, it’s restored along with its complete state (context, translation, contributors, etc.)

• Deleted: Deleted keys are removed with all their data - comments, translations, screenshot linking, contributors’ history, etc. Once the key is deleted, it’s no longer counted against the key limit, and it’s impossible to restore it.

If you are running over the source key limit, you can consider deleting deprecated keys. However, be sure that deleted keys are no longer necessary for your project, as you cannot restore them if needed, and all the associated data is also deleted.

It’s not only about the translations you can easily store and restore if needed when using deprecated keys instead of deleting them, but also about context information, comments, user interactions, etc. Once the key is deleted, it’s no longer counted against the key limit, and it’s impossible to restore it.