In-app copy editing
Our in-app copy editing feature makes it easy and safe for writers to edit the content in the actual source code. It's writer and developer friendly.
Our in-app copy editing feature makes it easy and safe for writers to edit the content in the actual source code. It's writer and developer friendly.
With our GitHub app, development teams make your app string files available for writers to search and edit. The setup only takes a few minutes (instructions here) - no custom API integration required. Strings can only access the apps' strings files your developers identify, not any other source code.
Quickly find content in your app. See exactly what your customers are seeing without bugging your developers or wondering if your design files are up-to-date.
Edit your app content in plain language. No coding required.
When you’re done editing, Strings automatically generates code updates and sends them as Git pull requests to your development team for review.
After your development team reviews your changes, they merge them into the source code to include in the next build.
No, Strings is a complement to the design tools and processes your team currently uses. Once you’ve finalized any copy changes with your team, Strings makes it easy to get those changes to your users. And it minimizes the time your engineering team has to spend managing copy.
Strings currently supports Android XML string files, iOS localization string files and web JSON string files. For the in-app editing feature, your app copy needs to be centralized in standards-based resource files (not hard coded in the source code), which is the common practice for app development.
We use a standard GitHub app to connect the string files to Strings for search and editing. It's a simple integration that only takes a few minutes. We currently support integrations with GitHub and are planning to add Bitbucket and Gitlab in the future. If you’re using a different VCS, please email us at contact@strings.design so we can prioritize other VCSs accordingly.
No, we do not require developers to change their development process or migrate data outside their code repositories. Strings allows writers and other non-developers to make changes to in-app copy without implementing a CMS.
There are many different types of translation software solutions available so there is no one-size-fits-all answer. If your string files are stored outside your code repository and get pulled into your apps at compile time or runtime, it's unlikely Strings can access those files or create pull requests for edits. If, however, your translation software pushes the language files back into your code repository once a new translation is available, Strings would work just fine since it's automatically synching the linked string files from Git.
