Everything You Need to Know about derivedStateOf()

🏆 My Online Courses
stevdza-san.com
☕ Buy me a Coffee
ko-fi.com/stev...
📝Medium
/ stevdza-san
💻 Github
github.com/ste...
📸 Instagram
/ stevdza_san
💎 Become a Premium Member
/ @stevdzasan
Watch the video and learn everything that you need to know about a side effect called derivedStateOf. Remove all confusions, but be sure to watch the whole video until the end. Ejoy and don't forget to leave a LIKE, it means a lot. :)

[@jackli1924]

You always explained tech so concise and through. Great job! Gratitude!

[@AndrewDChristie]

Thanks!

[@David-zb8br]

This channel is a gem for us android devs, never stop uploading

[@StevdzaSan]

Thanks buddy! 💚

[@muhammadirvan8655]

Thanks for sharing Stevdza-San, this relearn for me much deeper and i remember using this for pagination list. It really helps to know when state is really changing if user scroll down to bottom of the screen. Keep it up!

[@mieszkokozma4239]

No offence, but I think that this video could be done differently, so it actually explains when it's worth to use derivedStateOf and show some real world scenario of it being used. Basically you want to use derivedStateOf, once you want your composable to recompose LESS FREQUENTLY than the original state update. This might be the case for example when you're showing a value of Slider in a Text component. Slider updates are emitted very frequently and with high precision as a float, where you might want to only update Text once the value changed by at least 0,01. Then you could use derivedStateOf, round the state value into 2 decimals in its body and use such state in your Text. It'll recompose less frequently than the slider value updates.

[@jaelsonwagner]

Nice sample suggestion.

[@baharudinmaulana78]

Amazing, ibhope you always well, your content is very inspiring for me,

[@salvadorjohndeniel]

Thank you for this.

[@pankajthapa8957]

Good explanation on uses of derviedStateOf() keep it up

[@StevdzaSan]

Thanks 👍

[@dev_jeongdaeri]

Super cool

[@chirantanchaudhury2809]

Very helpful 👍🏻

[@VictorFarkas-fp2gl]

Nice one 👍

[@StevdzaSan]

Thanks ✌️

[@entrealist]

I did understand nothing to be honest. It so easy to get confused by just using "by remember" and "= remember".. why mutableState is not derived by default?

[@im_swapnil_musale]

Hey maybe I'm wrong but previously log was getting printed because of isn't in the remember body And later on you have added calculated log inside remember that's why it's not getting changed

[@StevdzaSan]

You gotta explain that a bit more, since I don't know on what exactly are you referring to in the code, there were a lot of logs.

[@mehulbisht9708]

@@StevdzaSan he basically means that, in the starting of the video you just had the `count` variable's state inside the `remember` block and the log statement with `LOG READ` tag was outside it, but there were not any log statements in that same `remember` block. But his point isn't valid here, as it has nothing to do with the log statement being inside or outside the remember block, since that log statement which has the `LOG calculated` tag only gets printed when the `calculation` variable is assigned a new value, which in turn depends on the `count > 3` condition to have changed atleast once :)

[@xabutencolorado1587]

This doesn't work out the way I expect

[@Briogus]

This wont work buddy. I wasted my time,