If you ever need an access to localized strings from your KMM modules: https://medium.com/xorum-io/simple-string-localization-in-kmm-beaffc5e7a17?source=friends_link&sk=3d6d3f62b7851ca412f09d49a03d89f7

If you visit the page https://developer.android.com/reference/android/content/res/Resources#getIdentifier(java.lang.String,%20java.lang.String,%20java.lang.String) you can read

Note: use of this function is discouraged. It is much more efficient to retrieve resources by identifier than by name.

Yes, totally depends on your needs.

Why just not use https://github.com/icerockdev/moko-resources ?

Doesn't work for us because we already have our strings provided by native modules with 3rd party integrations for translations. Shortly, we don't want to share strings between iOS and Android, but access some of them in KMM modules.

Don't look up Android resource identifiers by string name. It's slow enough that it shouldn't be used in anything more than debug utilities or toy apps. The comment is downplaying the inefficiency.