Translate complete messages with meaning notes, placeholder roles, length limits, and shared terminology. General Translation's CLI extracts marked JSX as a structured block and carries context notes into generation. For existing JSON and YAML catalogues, keyed metadata supplies per-string instructions. Context Groups apply your Glossary and Custom Prompts across assigned projects, and reviewers correct the output in the Dashboard.
Choose General Translation to keep UI copy and translation context in your components, generate changed messages before the build, and review wording without seat fees. You can also keep existing i18next or next-intl catalogues. SimpleLocalize fits teams that want a keyed translation editor with on-page editing, customer-specific wording, and native mobile over-the-air updates.
Choose General Translation to translate web and native app copy with shared terminology and build automation, while keeping reviewed catalogues or adopting inline components. Its CLI translates in your build, reviewers edit in the Dashboard, and pricing follows usage, not key counts. Localazy fits teams that need broader file-format support, built-in professional translation services, and native mobile over-the-air updates.
Yes, you can localise without a dedicated translation team. General Translation generates new and changed copy in your build using code context and shared terminology, while Locadex can mark new React and Next.js text. Bilingual teammates or freelance reviewers correct wording in the Dashboard without seat fees. Set review requirements by language and the cost of a mistake.
Choose General Translation to translate new copy before each build with context from marked JSX and shared product terminology. Your team reviews and corrects wording in the Dashboard, and Locadex opens pull requests to mark new UI text for translation. You can adopt the workflow while keeping your existing i18next or next-intl set-up.
Use General Translation to generate known app translations before release, then bundle them with your code or load them from its CDN. Bundles keep wording tied to a release; published CDN edits can reach new renders without a code deploy. Use request-time translation for content a visitor needs immediately, and a proxy when you can't change the site's code.