# ios


03/16/2022, 12:46 PM
Coming from an initially Android project, how to build language localisation into the iOS version when strings are called from common code? I know there are libraries for that, I'm wondering more about building it myself, it's (perhaps) not hard. It's easy to build a resource manager to dispense strings, but my main blocker is that, in contrast to Android, iOS seems to key strings from a main language version and I'm not sure how to square that with the "string name" strategy taken by Android


03/16/2022, 2:57 PM
As a person who likes to do things myself (I made multiplatform Date, Files and Uuid libraries), multiplatform localization is definitely one of the top things I would use a library for instead of trying it myself, especially if using a service for translation. I really don’t like the way iOS does it
🙏 1

Göksun Önal

03/17/2022, 7:59 AM
Most of the kmp libs use the "string name" from xml for the generate localization file for ios with "key string". Are you thinking more programmatically approach or using resource file with different extensions more like what android does ?


03/17/2022, 9:57 AM
It looks like I need to change what I've done, so I'm not fixed on one idea, the less change the better though. It's not a large project, but I have an increasing number of translations. It looks like Moko Resources would allow me to just move the android files I already have, which seems easy. What else is good?