How to implement flow into Android MVI + Compose with an UI State data class
I am creating a screen that presents a list of items. This list of items come from the internet in a paginated response, so I am trying to use PagingData and Pager to do it, but just can’t find the correct way to pass that flow into the composable while mantaining MVI architecture.
Is decision-logic inside Android Composable functions a bad idea?
Regarding Android Jetpack-Compose it is common practice to put your logic-parts inside your view-model.
Thats why I am using UI-States to abstract my businesslogic from what I display.
But where should I put necessary “visual-decision-logic” at.