So I've read this interesting <article about effec...
# compose-android
m
So I've read this interesting article about effective Text handling in compose. But I'm affraid it brings more questions that solutions. If I already have some screen state thats being backed by flows ( live/rx by what matters) and observing it as state in compose. If I want to apply this article suggestions does that means that I need to split the state associated with a text field and expose it as a State properties in new VM while also keeping the reactive stream for the rest? ( And thus in compose I observe the reactive one and the properties?)
more over whats if my "Text" associated state is dynamic, like a list of fiends name that I need to fill ( and that least is provided by arguemtns or fetched from our backend) How would you model that