Feature requests

When a translated string is identical to the source string that indicates that the translation is still pending. I believe there is currently no way to tell for which translations the translation is identical to the source? Two possible places in which it could be implemented (either or both): Filter in the list/table view As a QA Check

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.

It would be useful, if the default prover could be specified per project. Currently the app always falls back to google translate, and I have to set it manually every time to my desired provider (openai)

Add an option to change the default nesting delimiter (.) to another char or string.

With Crowdin it is possible to upload multiple screenshots per translation key - with SimpleLocalize this seems currently not possible? The reason this is desired is that often keys are re-used in multiple different places, and it makes sense to show screenshots for all use cases for each string to give translators the complete context

Automatically remember the last used import and export options. Add a shortcut to reapply previous configuration without manual setup.

Add a way to show changes directly in the portal using a standard green (added) and red (deleted) diff viewer before importing translations. Before Upload: Show a preview of what will change before the user uploads new translations. After Upload: Add a diff viewer to the Activity Log and Rollbacks so users can see what changed between versions.

Add a a new view to the translation editor that displays nested keys in a tree view. Make it work for namespaces too.

It would be nice if we could send out scheduled QA summaries to the translators that point out quality issues in their translations so they are more aware of them.

Introduce a Git-like versioning and branching system within the Translation Editor, allowing teams to create isolated environments for translation updates while maintaining a simple, non-technical user interface.