I see that this is the question which was asked before, but what is the current best solution on sharing string resources + localization between platforms? Is there any? Does everyone use
? Or doesn't bother and duplicates?
04/21/2020, 12:57 PM
so, if you allows me give you an suggestion, I wouldn't do that (sharing UI stuffs) because each platform has it specific solutions
I prefer don't share UI stuffs
what I do in this case is returns data that can be parsed to strings in the client side (like enums, or objects)
04/21/2020, 1:05 PM
got it! I want to gather opinions on this matter 🙂
04/21/2020, 1:10 PM
Going to use moko-resources (testing it ATM). Have one place to keep all localizations looks promising.
04/21/2020, 3:21 PM
I'd be interested to try it too, looks kinda complex, but maybe it's a tradeoff. Also I'd like to know how it will work out in the long run, but only time will tell...
04/21/2020, 4:08 PM
It's mostly build time tooling as far as I can see:
• take strings from MP project
• merge into platform file
• have expect class with constants
• generate actual class to access the strings via constants using platfrom specific way