Commenting & review

StringJet attaches comments to each string key inside the web editor. That keeps feedback next to the translation work — not buried in email or chat — so design, localization, and engineering share one context while keys evolve.

Open the app at https://app.stringjet.com. Comments complement the editor table and sit alongside imports and exports for a full localization workflow.

Comments on each key

From a row in the translation table, open the comments panel for that key. Threads accumulate on the key so historical discussion stays findable when someone revisits the string later.

Locale-scoped feedback

Scope a comment to all locales or to a single locale when feedback applies to one translation. That reduces noise for teams that ship many languages in parallel.

Review without leaving context

Because comments live in the same UI as edits, reviewers can confirm wording, flag terminology issues, or align with marketing before strings flow to OTA bundles or repo exports. Team membership and roles are covered on Team & access.

FAQ

Who can comment?

Anyone on the project with access to the editor can participate; exact permissions follow your role and project settings.

Are comments part of OTA payloads?

OTA bundles carry runtime string data for your apps; use comments for team coordination. See developer docs for bundle shape.