4 ms·
Neat! Seems to be looking like a more basic and unified translation management system, but it's unclear whether it actually supports multiple locales as a top-l
by madeofpalk 5y ago
Neat! Seems to be looking like a more basic and unified translation management system, but it's unclear whether it actually supports multiple locales as a top-level feature, or just through "hey here's your different JSON files".
> FlyCode identifies all the text segments in your product
I'm dubious of this claim to be honest. Identifying JSXText is one thing, but does it handle when you have UI text in props? How does is distinguish labelColor="red" from label="Username", if at all?
- iddan 5y agoHey there, founding engineer at FlyCode here. FlyCode is treating multiple locales as a first-class use-case. Some of our major customers use FlyCode for managing multi-locale applications. As for identifying all the text segments: what you are saying is true. For our beta we limited the text identification for JSXText only (for the React use-case) but we are certain we can identify more editable text in props using well-known names, looking into their type-defs or letting devs define which props should be exposed. This type of feedback and demand from our users that will bring our support to the next level! Like many creators we are trying to apply the Pareto principle [0] and make most of the copy of apps editable now. I agree the phrasing “FlyCode identifies all the text segments in your product” could be improved. [0]: https://en.wikipedia.org/wiki/Pareto_principle https://en.wikipedia.org/wiki/Pareto_principle