Features in active development

In addition to everyday bugfixes and tweaks, this is what we're working on right now.

Deployment tools

We recently released a range of new developer tools for notifying and publishing to external systems. This work is on-going as we build out the available options and receive feedback from customers.

Translation memory

We know that TM features have been lacking in Loco. Generally we're focussed on developer tools (as opposed to translator tools), but we are working on translation memory.

Audit system and rollbacks

This is the biggest feature in long term development. A new audit system will track every single change made in each project. This will provide a much-improved "activity" feed, and a dedicated UI for filtering activity by various criteria including time, language and individual team member. By tracking every single change in detail, you will be able to undelete lost items and even perform point-in-time rollbacks of entire projects.

Planned for future development

In no particular order, these features are planned for development over the coming months (and years). We can't give time estimates for new features because priorities are constantly shifting according to demand. If you're interested in a particular feature or have a new suggestion, please let us know.

• API keys are under review
  We plan to support multiple keys per user and introduce project keys that don't get revoked when the key owner disappears.

• Asset attachments
  Assets and translations should have the ability to attach file-based data such as screenshots.

• Role-specific workflows
  Individual translator roles should be configurable to automatically flag changes made. e.g. junior role marks all as "unapproved".

• Better export filtering
  Exports and interfaces can only filter on tags and translation states. Various other data should be filterable including the "context" field, date ranges, etc...

• Import file tracking
  Loco's import system was developed to simply load content into a project. As such it doesn't track individual strings against the files they belong to. It's proposed that files should also be a taxonomy, and it should also be possible to reconstruct a specific file from a "skeleton" given changed translation content.

• Jobs workflow / API
  It's common for Loco users to export and import files in order to work with third parties that prefer to use their own software tools. A dedicated "jobs" system would provide a way to package up work that needs doing and send it off for completion. It would also help with the re-import and approval processes.

• Git hooks and string extraction
  The import process should be able to detect code changes in Git repositories and extract new strings into Loco. Initially this is likely to be a PHP feature tied into the WordPress plugin, but could be widened out to other languages.

• Team discussion
  The current commenting system requires an overhaul. A better system is planned that will provide a fuller featured team chat and a better notifications system for team messages.

• Corporate SSO
  We plan to augment the current SSO options with corporate SAML provisioning.

• Xcode string variations and substitutions
  We support .xcstrings files, but this is limited to compatibility with Loco's existing feature set, which doesn't include string variations. See current iOS and Xcode support.