David Nedrow
07/26/2024, 7:06 PMVlad Mircan
07/26/2024, 9:33 PMcompose-multiplatform
resources still need to be interpreted by composeFunctions
.
So for something like a picture for example, even if the iOS
module gets its hands on the DrawableResource
object, it can't do much with it.
Things are a bit different for strings & colors though as you could think of them being passed down as `POJO`s. With that being said, in order for those resources to react to changes (localizable strings for example) you would still have to invoke a mini compose
scope on iOS
and save the result you got from compose.
At that point better to just forego compose-multiplatform-resources
and if you really want to share colors & strings, just create your own instances of classes of strings & colors. And observe configuration changes on the native apps and ask for a new version of the resources every time they change.