Want to understand how recompose work in following...
# composea
aniruddha dhamal
03/24/2021, 2:28 PMWant to understand how recompose work in following case. In case, uber state from view model is directly passed to all composables instead of passing state that individual composable need. Would that cause recompose on all composables? In the end, it will be calling basic composable (e.g Text) which won't trigger to regenerate UI but does it have any impact on performance issue since parent composables are revomposed? Or its just best practice to send the state what individual composable needs.
j
julioromano
03/24/2021, 2:30 PMI remember I had a similar discussion some time ago, posting it here hoping it may help you: https://kotlinlang.slack.com/archives/CJLTWPH7S/p1611232921023400
julioromano
03/24/2021, 4:33 PMa
aniruddha dhamal
03/24/2021, 4:42 PMThanks a lot for the link @julioromano! I was able to grab most of it.
It means recompose will be called on all of the composables so it's better not to pass uber state, since it does take a toll to invalidate that compose based on 1st example from the thread. 2nd example passes specific state so it skips recomposition.
correct me if i'm wrong.
j
julioromano
03/24/2021, 4:58 PMIn pure theory yes, but in practice this will never translate into a performance penalty, so you shouldn’t let this kind of thoughts dictate how you write your code. This is premature optimization which in 99% of the cases is useless.
Please take a look at this thread which had a question similar to yours: https://kotlinlang.slack.com/archives/CJLTWPH7S/p1616602800058000
đź‘Ť 1
a
aniruddha dhamal
03/24/2021, 4:59 PMThanks a lot @julioromano! đź‘Ť
3 Views