Kebbin
11/06/2021, 11:20 AMViewModel
, as described in the Guide to app architecture. Then, your composables are responsible for transforming the current application state into a UI every time the observable data updates."
And again here further down:
"Recomposition:
In an imperative UI model, to change a widget, you call a setter on the widget to change its internal state. In Compose, you call the composable function again with new data. Doing so causes the function to be recomposed--the widgets emitted by the function are redrawn, if necessary, with new data. The Compose framework can intelligently recompose only the components that changed."
I'm only an amateur, but I'm loving this a lot! 🤓darkmoon_uk
11/06/2021, 11:32 AMState
concept offered by Compose and it'll take care of recomposing the parts of your UI needed.Kebbin
11/06/2021, 11:33 AMdarkmoon_uk
11/06/2021, 11:33 AMKebbin
11/06/2021, 11:33 AMdarkmoon_uk
11/06/2021, 11:34 AMKebbin
11/06/2021, 11:34 AMdarkmoon_uk
11/06/2021, 11:35 AMKebbin
11/06/2021, 11:35 AMdarkmoon_uk
11/06/2021, 11:35 AMKebbin
11/06/2021, 11:36 AMdarkmoon_uk
11/06/2021, 11:37 AMKebbin
11/06/2021, 11:37 AM