Feature requests

Implement a plugin/library/workflow for the native mobile SDK that would allow users to update translations without having to make a full release of their apps. Implementing this feature would likely require to hire Android/iOS developers. Feel free to contact us if you think you can help us with this task.

Add an option to include comments (Code Descriptions) in the exported translations. For example, when working with .xcstrings/xml files, replacing the previous translation file with the export causes Xcode/Android Studio to no longer display comments for the strings. Currently, the workaround is to merge the project's existing file with the updated file using jq or similar tools while preserving the comments field.

We could allow users to add custom properties to translation keys and translations, store them in SimpleLocalize, and return them in the output. This feature might simplify some workflows by providing additional context or metadata, making it easier to manage/filter/sort on the client side.

During import and export from the 'Data' tab, verify user access permissions for languages, customers, tags, editing, and other relevant settings.

It would be great if we could choose to only publish selected translation keys to the individual stages.

Add option to the CLI to extract translations from HTML elements that has “data-i18n-key” attribute directly from the URL, list of URLs, or sitemap.

Currently, there are three options to choose from: "Only default language" "Any language except default" "Any language" The goal of this feature request is to add an option to select one or more specific languages that will trigger the automation.

Add WYSIGWYG to the text editor to simplify Markdown support for non-technical users.

I accidentally made the mistake of having a translation key with a trailing space. Finding my mistake was quite a challenge. My suggestion would be to always trim translation keys, meaning no leading or trailing spaces, in case the user accidentally adds a space at the beginning or end.

An option to use one key in multiple projects - show it as shared translation key. When translation is updated in one project, ask if it should be updated in other projects where the translation key is used.