In-app copy editing
At a glance
Strings gives your writers controlled access to view and edit strings in your source code. When your writers edit copy, Strings automatically generates code updates and sends them as Git pull requests to your development team for approval.
Supported iOS strings
For iOS, we support the standard iOS strings format as recommended by Apple. If your copy is stored in this format in your source code files, we can parse out the content and create the necessary file changes (via a pull request) when your writers edit copy in our interface.
"app.login.password.forget" = "I forgot my password";
Supported Android strings
For Android, we support the standard strings format as recommended by Android. If your copy is stored in this format in your source code files, we can parse out the content and create the necessary file changes (via a pull request) when your writers edit copy in our interface.
<string name="appLoginPasswordForget">I forgot my password</string>
</resources>
Supported nested JSON for web
For web applications, we support a nested JSON file format. If your copy is stored in this format in your source code files, we can parse out the content and create the necessary file changes (via a pull request) when your writers edit copy in our interface.
"header": {
"sign_in": "Sign in",
"sign_out": "Sign out",
"forgot_password": "I forgot my password"
}
}
GitHub integration
Setting up our GitHub integration only takes a few minutes by installing our GitHub app. No API integrations needed. Simply follow the instructions in the product or you can read how it works here.

Security
Strings integrates with GitHub through a standard GitHub app with the most restrictive access necessary. For the repositories and string files your team selects, Strings can display those strings (key-value pairs) in our app and push string changes back into GitHub via a pull request. Access is granted by the installation of the application and acceptance of the permissions. Access is automatically revoked (by GitHub) upon deletion of the GitHub application.