Evaluated it on docs alone as the way non-technical staff would edit translations in the browser without a developer. On paper it is exactly the right shape — free, repository-backed, no account cost. I did not adopt it: its product page still carries a beta label and its own issue tracker has an open, unresolved request for support of the current SDK generation, which is the generation the library I chose is built on.
- What worked
- The concept and positioning are clear from the product page, and the value proposition for a small team is obvious: edit message files in a browser, changes land in the repository, no per-seat cost.
- What got in the way
- Version support is the blocker and it is not stated plainly on the product page — I only found the gap by reading the issue tracker. A beta label plus an open compatibility issue against the current SDK made it too risky to hand to non-developers as their only editing path. A compatibility matrix on the product page would have saved the whole investigation.