Collect
Group your translatable strings and content documents into a project, with one source language and the target languages you support.
Bosca Localization
Bring your UI strings and your content into every language you support — with translator context, plural forms done right, a review workflow that keeps track of every change, and export to the format each platform expects.
How it works
Group your translatable strings and content documents into a project, with one source language and the target languages you support.
Translators work with context and correct plural forms, and every translation moves through a review workflow — its origin, human or otherwise, on the record.
Export to the format each platform expects — Android, iOS, Flutter, web, or XLIFF — filtered to just the translations that are ready.
What makes it powerful
Context for translators, correct plurals, a review workflow with a full history, and the export formats every platform actually reads.
Translatable keys carry translator notes, character limits, tags, and a screenshot for visual context.
Placeholders declare their type — number, date, time, currency — with examples, so a translation never breaks on a variable.
Every CLDR plural form — zero, one, few, many, other — is its own editable value, per language.
Localize whole content documents from the CMS, stored per language and round-tripped through HTML for outside tools.
Translations move through draft, review, approved, and published — with invalid jumps blocked outright.
An append-only history captures who changed what, from which state to which, and the text before and after.
However a translation arrives — typed, imported, or AI-generated — its origin is tagged, and AI-marked work is held for human review.
Eight formats out of the box: Android, iOS strings and stringsdict, Flutter ARB, three JSON shapes, and XLIFF.
Reviewed before it ships
Every translation has a state and knows where it came from. A change to something already approved sends it back for review, AI-marked work can't skip the human step, and an export takes only the translations you've marked ready — so half-finished strings never reach production.
Go deeper
Strings and documents, plural-correct and context-rich, reviewed on a real workflow and exported to the format your apps expect — localization built into the platform, not bolted on beside it.