About StringJet
Localization that fits
every product team.
We built StringJet because professional localization tooling shouldn't require an enterprise contract. Fast OTA delivery, a real collaborative editor, and transparent pricing — for teams of any size.
Why we built this
Shipping a fix shouldn't take three engineers and two weeks.
Every team we'd worked on had the same problem: a translation mistake found the day after a store release. A copy change that needed a designer, a developer, a PR, and a two-week review cycle before it reached users. Tools existed — but they were built for enterprise budgets or too shallow for real production workflows.
StringJet was our answer. We wanted over-the-air updates that work reliably in production, a collaborative editor that feels like a real product tool rather than a shared spreadsheet, and SDKs that developers can integrate in an afternoon — without negotiating an enterprise deal.
We keep the platform lean and the pricing transparent because we're a small team building something we'd genuinely want to use ourselves.
Our mission
Make professional localization accessible to every product team — from indie developers to growing businesses — without sacrificing the reliability that production apps require.
Fair pricing
Four self-serve tiers from Free to Business — no seat minimums, no hidden overages. Pay for what you actually use and upgrade when your team grows. See pricing →
Utrecht, Netherlands
We're based in Utrecht — a compact, well-connected city in the center of the Netherlands. Our team works in European time zones and serves customers worldwide.
The team
The people behind StringJet
A focused founding team with complementary skills — engineering, design, and relationships — and a shared belief that localization tooling can be both powerful and approachable.
Armijn Vink
Lead Developer
Architects the platform backend, SDK layer, OTA delivery infrastructure, and developer tooling. Keeps the system fast, observable, and straightforward to integrate across Android, iOS, Flutter, and web.
Tom Gielen
Lead Designer
Shapes the product experience — from the web editor and Figma plugin to this website. Focused on interfaces that feel obvious from the first time you open them and stay out of your way as your team grows.
Sara Azizi
Sales & Marketing
Manages partnerships, customer relationships, and business development. The bridge between what StringJet can do and the teams who need it most — keeping feedback close and the roadmap grounded.
Release history
How StringJet has grown
A record of what shipped with each major release — from platform launch to the latest SDK improvements.
Android SDK — view-tree patching & performance
Major rework of Android XML view-tree patching. OTA translations now apply before the first frame using a pre-draw listener, with memoized patch indices and debounced follow-up passes so RecyclerView and back-navigation stay consistent. Sync is non-blocking. ViewPump integration replaces the reflection-based AppCompat hook for a stable, properly-declared approach.
Android SDK — AppCompat, Compose & async sync
AppCompat support so OTA strings resolve inside Jetpack Compose. Room-backed translation cache with in-memory snapshot and async warmup. Fragment lifecycle callbacks for back-navigation patching. Translation-updated listener for Compose state invalidation after a successful OTA fetch. Transitive Room and SQLite dependencies declared so Maven consumers don't need manual dependency wiring.
Android Maven publishing & Apple SDK improvements
Android OTA SDK published to Maven Central as a single self-contained AAR with Room-backed translation caching built in — no unpublished project dependencies for consumers. Apple Swift Package updated with clarified string resources terminology covering both legacy Localizable.strings and modern String Catalog formats. Developer documentation fully rewritten.
Platform & SDK launch
StringJet launched publicly. Web editor with multi-locale support, string key management, project and team setup, and import from Android XML and iOS strings format. First OTA SDKs shipped for web, iOS (both xcstrings and Localizable.strings), and Android — enabling over-the-air translation delivery without an app store submission from day one.
StringJet founded in Utrecht
Three people, one problem: localization tooling that works for teams who aren't enterprise. Development started on the editor, OTA delivery system, and cross-platform SDK architecture.
Want to see StringJet in action?
Sign up to explore the platform, or read the platform overview to see what StringJet can do for your team.