Im using `composeResources` for all the strings in my app. Generally very happy with it, but the log...

# compose

[Zoltan Demant]

Im using composeResources for all the strings in my app. Generally very happy with it, but the logic that "Okay, I need some of my strings.. Ill just add compose to my module" feels awkward.
• Is there any work being done to separate this from compose?
• Any advice to make it less awkward?
Its just a mental thing, but just like bringing in compose in order to add @Immutable to my domain layer would feel wrong, this too feels wrong to me.

[Konstantin Tskhovrebov]

KT-49981 Multiplatform API to access library and application resources

[Zoltan Demant]

Can't believe no AI could find that. Thank you!

[Colton Idle]

i haven't read this yet. but i saved it for reading at a later date. maybe helpful. https://chrisbanes.me/posts/multiplatform-strings/

[Zoltan Demant]

Oooh, Ive read that but I think I need to read it again! Thanks!

[Colton Idle]

let me know if you it answers your question at all. maybe it'll save me some reading. lol

[Zoltan Demant]

I'll stick with compose resources for now, but really digging twine having all translations in the same file. Ai can probably do some great work with that. Good read though, wish I had time to make the jump and give it an honest try 😁