A modern programming language that makes developers happier.

kotlinlang

Good morning, coders— I have a question. Regarding resource management via compose.component.resources, why was it decided to tie this library exclusively to Compose? By doing so, I can’t use it for targets like Linux, Windows, or watchOS/tvOS.

Let me explain my situation. I’m developing a very large project split into multiple modules. In the internet-connection module—where I use almost nothing but Ktor—I’d like to handle standard error cases by localizing the messages directly within the network module, centralizing translation. However, to use Compose’s Resources I’m forced either to drop some targets or to come up with very awkward workarounds.

With that in mind, is it possible to create a version of compose.component.resources for all platforms, decoupling it from Compose?

That's why I stick to moko resources. Those work with or without compose and support svgs in all targets i need(ios/android)

<https://github.com/icerockdev/moko-resources|https://github.com/icerockdev/moko-resources>

<https://youtrack.jetbrains.com/issue/CMP-4495/Use-compose-resources-without-skiko-on-Js-and-Wasm-targets|https://youtrack.jetbrains.com/issue/CMP-4495/Use-compose-resources-without-skiko-on-Js-and-Wasm-targets>