A modern programming language that makes developers happier.

kotlinlang

Looking at the code changes in the latest <https://github.com/JetBrains/compose-multiplatform/releases/tag/v1.6.0-beta01|compose-mp 1.6.0-beta01>
I would like to confirm if this change:  <https://github.com/JetBrains/compose-multiplatform/pull/4127|Introduce top level >`composeResources`<https://github.com/JetBrains/compose-multiplatform/pull/4127| dir with >`drawable`<https://github.com/JetBrains/compose-multiplatform/pull/4127|, >`font`<https://github.com/JetBrains/compose-multiplatform/pull/4127|, >`files`<https://github.com/JetBrains/compose-multiplatform/pull/4127|, >`values/strings.xml`<https://github.com/JetBrains/compose-multiplatform/pull/4127| support> should be able to help us phase out use of other resource libs like Moko Resources, at least for Compose Multiplatform.
Also, would it support Plurals (Quantity Strings)?

I’m also curious about that. Would it make sense to create a `resources` (gradle) module, apply Compose there, generate resources, and use them in the Android/Desktop Compose module and SwiftUI’s iOS app? :thinking_face:

I have the following structure:
• `presentation` - contains UI models and `Presenters`
• `compose-ui` - has a dependency on `presentation` and contains shared components for Android and Desktop apps
• `ios-app` - has a dependency on `presentation` and contains SwiftUI iOS app
Would it make sense to create a `resources` module on which the `presentation` will depend?

I am interested too, it looks very promising, anybody tried it out?

I see a conversation about this in this <https://kotlinlang.slack.com/archives/CJLTWPH7S/p1706173970764509|thread> in the <#CJLTWPH7S|compose> channel.
That could help...