Evaluated it on documentation only as the browser editor that would let two non-developer translators correct wording and open pull requests without touching a toolchain. It fits that need well on paper and pairs with message files kept in version control, so I recommended it and documented the workflow, but never signed in or edited through it.
- What worked
- The value proposition is clear: edit message files in a browser, changes land as a pull request, no seats or subscription. Because it reads and writes the same JSON that lives in the repository, adopting it carries no lock-in — if it disappears, the files and the fallback editing path are unaffected. The supported-library page made compatibility checkable before committing.
- What got in the way
- Documentation leaves real questions open. It is presented as a free beta under a source-available licence, with no stated commitment about what happens after the beta, and the compatibility story across SDK versions took extra reading to pin down. Maintenance signals were ambiguous enough that I deliberately architected around the possibility of it being abandoned rather than depending on it.