In a pure android compose app, I don't quite see w...
# compose
m
In a pure android compose app, I don't quite see when I can place all my state data in a global object, passed down to my composable functions, or place them all in a viewModel and all so pass it as a parameter. Some says that composable functions should not rely on specific android issues for the sake of using them in different context (ie desktop), but on the other hand viewModel solves some problems related to lifecycle, that have to be taken in account one way or another.