Has anyone one found the best way to manage state ...
# composep
Pau Marzo
05/26/2025, 10:06 PMHas anyone one found the best way to manage state in Compose in deep Composable trees (especially in desktop or web)?? I find myself that since all of my state is stored in a single data class, i only use a single viewmodel with all state and repositories but still it all "converges" into a single data class, making updates to state in Compose difficult to know when its recomposing or if its not recomposing enough (plenty of that 🙂 unfortunately). For example, a 3 pane composable screen, should i have a viewmodel for each of the panels and all those viewmodels modify (with thread safe functions) the state which can be split in different classes or is it better to keep a deep repository that holds all state? From the Compose perpective, its easier to use several viewmodels for each screen and "main layout like panels" for better state tracking but storing that data then becomes a nightmare....
u
ursus
05/26/2025, 10:47 PMits depends on what are you doing, if you have a single entry point of state being thrown into the UI, you do pay the diffing, but that should be just reference comparisons mostly so cheap..imo
z
Zach Klippenstein (he/him) [MOD]
05/27/2025, 2:52 PMI think libraries/patterns like Circuit, Workflow, etc are a good solution to this. AAC ViewModels are not very scalable.
2 Views