String Catalog is built for more than app strings.
Use it when your team wants one localization workflow that covers the product, the release, and the launch copy around it.
App Strings
String Catalog supports localization for core app-string formats such as:
This is the foundation for product copy that ships inside the app itself.
Release Notes
String Catalog can also localize release notes from one base-language draft into your active project languages.
This is useful when you want to:
- Write one source note per release
- Generate localized App Store and Google Play release notes faster
- Keep launch messaging aligned across markets
For the full workflow, see Localize Release Notes in String Catalog.
App Store and Google Play Metadata
For launch teams, String Catalog can extend beyond the app and into store listing copy.
That includes workflows for:
- App Store metadata fields
- Google Play listing fields
- Locale-aware review
- Export-ready output for handoff or publishing
For the full workflow, see Localize App Store and Google Play Metadata.
Human Review and Feedback
Localization quality is not only about generating text. Teams also need a way to review it.
String Catalog supports review workflows such as:
- Protected Terms (Glossary) for brand and product wording
NeedsReviewstatus for changed or questionable translations- Share links for translation feedback when you want outside reviewers to contribute safely
How These Work Together
Many teams use String Catalog across the full launch workflow:
- Localize app strings in native files.
- Localize release notes for the upcoming version.
- Localize store metadata for the listing refresh.
- Bring in human review where nuance matters.
- Ship through the same repo and release workflow the team already uses.
You do not need every workflow on day one, but the product is designed so they can fit together cleanly when your process grows.