Integrations

StringJet fits into a typical product stack in three lanes: design (Figma), repo-shaped files (imports and exports in the web app), and runtime SDKs (mobile and web). Together they cover handoff from design through CI to live apps.

Design — Figma

The StringJet Figma plugin runs inside Figma for key lookup, copy handoff, and per-locale previews. Install from the Figma community listing and link files from the plugin. See the full walkthrough on Figma plugin.

Version control — GitHub & GitLab

Connect a repository to pull translation files into StringJet and open pull/merge requests when you export. GitHub uses a GitHub App; GitLab uses OAuth on gitlab.com. See GitHub integration and GitLab integration.

Structured import & export in the web app

The Import tab accepts ZIP archives, single files (ARB, JSON, XML, strings, xcstrings trees), and folder picks for Android res, iOS .lproj, and similar layouts. The Download tab generates Android XML, iOS legacy strings or xcstrings ZIPs, Flutter ARB, or web JSON with language and platform filters. See the full format list on Imports & exports and I18N_FORMAT_SUPPORT.

SDKs & APIs

Developers integrate OTA SDKs for Android, iOS, Flutter, Compose Multiplatform, and web using the public project id and tokens from Project info. Platform setup lives on developer.stringjet.com — for example Android, iOS, Flutter, and React. Business plans add MCP and CLI automation for tools like Cursor — see MCP automation.

Project-level integrations

Inside each project, the Integrations tab in the web app is a marketplace of connected services and SDK documentation — including Figma connection status, OTA SDK guides, and MCP setup. Figma linking still happens from the design tool; the tab shows status and links to docs.

Open the product at https://app.stringjet.com · Plans