@@PhilippLackner Thanks to you bro, resourceful people are often bad teachers cause of human nature, you in other hand are damn smart and brilliant in the way you explain
Thanks for this! Although my mind couldn't absorb any of the discussed effect. Part 1 to 9 is clear and easy to follow as a newbie of Jetpack Compose. This part (Part 10) doesn't have any relevance in almost all discussed subjects in parts 1 to 9 that's why I couldn't comprehend. Maybe this should be moved in a more advanced playlist for compose. I will just skip to the next part hopefully I am not totally lost as I really love the tutorials. I'll take note on this effect handlers and when I got to the point when I already need this subject then I'll just get back here. Thanks Philipp! Cheers!
same kinda difficult... tried finding the prepared code (samples) to go over it... and couldn't find it. The code qould help, thought of buying the premium course, but if I don't understand the frrebee, not sure I will understand the paid course...) having the code wouldn't deter me from purchasing the paid course, maybe it would motivate me more
Just be careful, think of derivedStateOf just as you would mutableStateOf in a sense that it needs to be remembered! Otherwise this isn't remembered and in case of recomposition will just be called again from scratch. And overall it feels like your explanation on derivedStateOf could be improved a bit. You didn't mention anything about how it implicitly "subscribes" to the state objects that are being accessed in there, but doesn't have any mechanism to update itself when non-state objects are being read in its lambda are changed so it would then show stale data. I really suggest people to read the excellent documentation on these, it does a great job explaining with examples how they work.
THANK YOU SO MUCH, just this afternoon i was duct taping together my own event system from snippets of code i found online, but the one you show in LaunchedEffect part is so much better and cleaner! Thanks! The rest of the video is also great as well!
awesome video! just one simple thing I notest was he snapshotFlow using the distincUntilChanged(), actually the snapshotFlow itself is already handling it, so it will get the latest value of the state if its value is different, so in this case you dont need call the distinctUntilChanged. btw thanks a lot for this video it helped a lot to understand all of them
Months later, my webview was playing audio event after navigating away. Destroying it in DisposableEffect did the trick. Good thing I bookmarked this video 😁
Hi Philip - excellent again! How about a quickie example explaining delegation ("by") and when to use that. I find it very confusing and maybe you could shine some light on this.
quality videos after long time ......need more clean architecture full apps tutorial or compose tutorial..(animation ,canvas ,custom modifiers , custom layout..etc)
To be honest, I didn't understand the part when you talked about the view model and other and collection of flow, I guess, if someone can give me an idea ?
In my opinion, 19:00 is missing the point. produceState() uses LaunchEffect in the background so that's another difference. And basically the example with the flow constructor seems to be breaking the core principles of compose, it seems like it's doing backwards writes, you are going to end up with infinite recompositions. Saying this as someone who is trying to wrap my head around Compose. :D
I’m trying to run a recursive task every 15seconds (like call an api) on my jetpack screen, how can I achieve this with launched effect or any other Android class without using workmanager.
Thanks for your educational and helpful videos! The Android Studio theme that you’re using looks awsome, what is the name of that? ⭐️🧐 Cheers from Sweden 🍻
Hi Phillipp!! As always, top notch videos! Thank you! I have a question, I have a Composable function that creates a JFreeChart object which basically gets recomposed when ever its DataSet values are updated. But in that case, the entire JFreeChart object gets recreated again and again with each recomposition. So it appears to be a side effect. Is LaunchedEffect the more accurate choice to prevent that? Do I create the JFreeChart object with key1 = true and then simply let it observe its DataSet updates? Thanks!
Philipp, Hi! I love your content, thank you for that. I don't understand one thing. Could you please explain me ? Why cant we just use derivedStateOf everywhere since it optimizes everything ?
Sadly, all `SideEffect` examples strive to be so oversimplified, that neither of them actually demonstrates the real use case of it. Like: what would happen if you do this call without wrapping in `SideEffect`? This effect handler deserves better example.
So was I, but you can usually get the answers in the comments. This is a response from @tetsuoshiva: When you create a new Compose project, it creates a theme named "[ProjectName]Theme". Chances are the project was named "EffectHandlers", and "EffectHandlersTheme" is the theme that was created at project creation. Just write your project name instead of "EffectHandlers", followed by "Theme".
Hey, just finished course about multimoduling. Have a question - when services are needed? For example, if there are any pros for moving api calls to service, if these are periodic calls made with workmanager? Thanks)
Workmanager is needed when you have work that needs to be done reliably, even when your app is closed or the device restarted. Not for user initiated network calls
In your MVVM News App, how to refresh the news list using swiprefershlayout listener or when call news list api from onresume override method? I am new to MVVM architecture, please help me as i am calling the news list api in onresume but not in oncreate as i need to refresh the news list every time i came back to breakingnews fragment.
Hi Philipp, awesome video, thanks for the great content! Just a question, how would you implement a snackbar call after navigation? when i perform an action, the app navigates up and need to show a snackbar, but i am just not being able to do it... how would you do it?
What you can also do is have a scope = rememberCoroutineScope and a scaffoldState = rememebreScaffoldState in your App() composable and a Scaffold. Your composables should expect a showSnackbar: (String, SnackbarDuration) -> Unit parameter, that you can call (for example when navigating up) like showSnackbar ("Your snack message", SnackbarDuration.Short). Your navigation composable should expect the same function parameter so you can just pass it on to your actual screen composables when creating the instances. In the end your Scaffold in App can look like this: Scaffold( .. state= scaffoldState .. ) { .. YourNavigationComp( navHost =... showSnackbar = { message, duration -> scope.launch { scaffoldState.showSnackbar(message, duration) } }) } With this solution you have a snackbarScope scoped to the App() so your snackbar is still visible during navigation and in the new screen. (Obviously if you need a snackbar scoped to your screen you can implement the scope and Scaffold there). Hope I could explain it well and could help.
Your question inspired me to write an article about about the topic in Medium, because I had this same struggle some time ago. I can not post the link here but added it to my youtube bio.
On 7:02 you said that code in LaunchedEffect only once when screen composed for the first time. How another Event can happen in this case? E.g. it collects first event - ShowSnackbar and then Navigate event happens but you told that code executed only once
The launch effect block is executed once, so it subscribes to the flow once. But once a subscription is established the collect block will trigger with each event
@PhilippLackner In the LaunchedEffectAnimation example. How can `counter` change? It’s just an Int parameter and is never assigned to. Would the example work the same if the first argument to LaunchedEffect were `true`? Great videos, by the way; I’m working my way through the original Compose series and have learned a lot.
When you create a new Compose project, it creates a theme named "[ProjectName]Theme". Chances are the project was named "EffectHandlers", and "EffectHandlersTheme" is the theme that was created at project creation.
This side effect makes me think twice whet i should use this or maui csharpmarkup. Compose makes it so much complicated especially in example. Why not make normal oop. İnstead of frp in order to conpansate for downside of functional programming, they added remember state etc. How to cover a hole with another thing that also has a hole. Total bullshit..
![Jetpack Compose. Side Effects. Как управлять логикой в Compose? [Ru, Kotlin\Android]](http://i.ytimg.com/vi/NxwkaPdLQPk/mqdefault.jpg)
For me you are the best channel for Android development
Thanks a lot!
+++++
@@PhilippLackner Thanks to you bro, resourceful people are often bad teachers cause of human nature, you in other hand are damn smart and brilliant in the way you explain
Same for me.. 😂, I think this man deserves half of our salary 😂. Thanks @PhilippLackner!
Philipp is forever invited to my home for dinner. Such nice content and delivery.
❤️
The only 2 I found useful were LaunchedEffect and DisposableEffect. The rest of them were created to make the interviews harder.
Thanks for this! Although my mind couldn't absorb any of the discussed effect. Part 1 to 9 is clear and easy to follow as a newbie of Jetpack Compose. This part (Part 10) doesn't have any relevance in almost all discussed subjects in parts 1 to 9 that's why I couldn't comprehend. Maybe this should be moved in a more advanced playlist for compose. I will just skip to the next part hopefully I am not totally lost as I really love the tutorials. I'll take note on this effect handlers and when I got to the point when I already need this subject then I'll just get back here. Thanks Philipp! Cheers!
I had the same feeling!
same kinda difficult... tried finding the prepared code (samples) to go over it... and couldn't find it. The code qould help, thought of buying the premium course, but if I don't understand the frrebee, not sure I will understand the paid course...) having the code wouldn't deter me from purchasing the paid course, maybe it would motivate me more
😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😅😮😮😮😮😮
@Peter Fraga 😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮ㅣ😅😅😅😅😮😮😅😮ㅣ😮ㅣ😮😮😮😮😮😮😅😮😮😮😮😮😮😮😮😅ㅣ😅😮😮😮😮😮😮ㅑ😅😅😅😅😅😅😅😅😮😅😅😅😮😮😮😅😮😅😮😮😮😮😅😅😅😮ㅣ😮😮😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😮😅ㅏ😅😅😅😮😅😅😅😅😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😅😮😮😅😅😅😅😮ㅣ😮ㅣ😮😮😮😮😮😮😮😅😅😅😅😮😮😮😅😮😮😮😮😅😮😮😅😅😅😮😮😮😮😮😮😮😮😮😮😮😅😅😮😮😮😮😅😮😮😮😮😮😮😮😮😮
😮😮😮😮😮😮😮😮😮😮😮😮😅😮😅😅😅😅😅😮😮😮😮😮😮😮😮😮😮😮😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮ㅣ😅😅😮😮😮😮😮😮ㅣ😮😮😮😮😮😮😮😮😅😅😮😅😮😅😅😅😮😮😮😮😮😮😮😮😮😮😮😅😅😅😅😅😮😮😮😮😮😮😮😮😮😮😮😮😅😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😅😮😮😮😮😮😮😮😮😮😮😮😮ㅣ😮😮😮ㅣㅣ😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😅😮😮😅😅😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😅😮😮😮😮😮😮😅😅😅😅😅😅😅😅😮😮😮😮😮😮😮😮😮😮😮ㅑ😮😮😮😮😮😮😅😮😮😮😮😮😮😮😮😮😮😮😅😅😮😮😮😮😅😅😅😅😅😅😅😅😮😮ㅣ😮😮😮ㅣ😮😮ㅣ😮ㅣ😮😮😮😮😮😮😮😮😮😮😮ㅣ😮😮😮😮😮😮😮😮😮😮😮😮😅😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😅😅😅😅😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😅😅😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😮😅😮😅😅😅😅ㅣ😮😮
😮😮😮😮😮😮😮😮😮😮😮😮😮😮😅😮😮😮😮😅😅😅😅😮😮😮😮😮😮😮😅😮😮😮😮😮😮😮😮😮😅😅😮😮😮ㅣ😮
I always check on my notifications to make sure i did not miss a new video from this guy
Thank you Philipp , You explain contents with interesting examples.
Here is one of the best channel for android.
👏👏
Just be careful, think of derivedStateOf just as you would mutableStateOf in a sense that it needs to be remembered! Otherwise this isn't remembered and in case of recomposition will just be called again from scratch. And overall it feels like your explanation on derivedStateOf could be improved a bit. You didn't mention anything about how it implicitly "subscribes" to the state objects that are being accessed in there, but doesn't have any mechanism to update itself when non-state objects are being read in its lambda are changed so it would then show stale data.
I really suggest people to read the excellent documentation on these, it does a great job explaining with examples how they work.
Great point here.
I was struggling with this. Thanks for the video ❤️❤️
THANK YOU SO MUCH, just this afternoon i was duct taping together my own event system from snippets of code i found online, but the one you show in LaunchedEffect part is so much better and cleaner! Thanks! The rest of the video is also great as well!
Compose related videos always welcome
Thanks for the video. I appreciated all the examples and the simplicity of them for easier understandability.
awesome video! just one simple thing I notest was he snapshotFlow using the distincUntilChanged(), actually the snapshotFlow itself is already handling it, so it will get the latest value of the state if its value is different, so in this case you dont need call the distinctUntilChanged. btw thanks a lot for this video it helped a lot to understand all of them
Awesome, thank you!
bro you are awsome may god always send good days on your way.
Months later, my webview was playing audio event after navigating away. Destroying it in DisposableEffect did the trick.
Good thing I bookmarked this video 😁
Hi Philip - excellent again! How about a quickie example explaining delegation ("by") and when to use that. I find it very confusing and maybe you could shine some light on this.
Thanks for the idea, however right now i have tons of other videos in my pipeline 😄
Thank you for the video. I will watch all the Compose serie 👍
Top channel for genuine content on android after the Google android developer channel.
You are the few youtube channels that I have turned on notifications on :D You touch on very important points as always. Thanks.
Thanks man!
Seriously I was waiting for this video
Thanks 😊
Gem's channel , thanx man , wish you all the best in your life
quality videos after long time ......need more clean architecture full apps tutorial or compose tutorial..(animation ,canvas ,custom modifiers , custom layout..etc)
To be honest, I didn't understand the part when you talked about the view model and other and collection of flow, I guess, if someone can give me an idea ?
Thanks for sharing, really cool video!
Thank you philipp 😁
You're welcome
thanks for all
This stuff would be much easier with practical uses but great content as always.
In my opinion, 19:00 is missing the point.
produceState() uses LaunchEffect in the background so that's another difference. And basically the example with the flow constructor seems to be breaking the core principles of compose, it seems like it's doing backwards writes, you are going to end up with infinite recompositions.
Saying this as someone who is trying to wrap my head around Compose. :D
wow. such a good explanation.
I’m trying to run a recursive task every 15seconds (like call an api) on my jetpack screen, how can I achieve this with launched effect or any other Android class without using workmanager.
Hi, Philipp, great video!
What is yout Android Studio theme?
Thanks =)
Xcode dark
Best explanation video of this thanks bias god
Gym Shark should start sponsoring Philipp !!
Thanks for your educational and helpful videos! The Android Studio theme that you’re using looks awsome, what is the name of that? ⭐️🧐 Cheers from Sweden 🍻
Thanks, it's xcode dark 🙌
@@PhilippLackner Thank you very much! 🙏
Hi Phillipp!! As always, top notch videos! Thank you! I have a question, I have a Composable function that creates a JFreeChart object which basically gets recomposed when ever its DataSet values are updated. But in that case, the entire JFreeChart object gets recreated again and again with each recomposition. So it appears to be a side effect. Is LaunchedEffect the more accurate choice to prevent that? Do I create the JFreeChart object with key1 = true and then simply let it observe its DataSet updates? Thanks!
Philipp, Hi! I love your content, thank you for that. I don't understand one thing. Could you please explain me ? Why cant we just use derivedStateOf everywhere since it optimizes everything ?
Sadly, all `SideEffect` examples strive to be so oversimplified, that neither of them actually demonstrates the real use case of it. Like: what would happen if you do this call without wrapping in `SideEffect`? This effect handler deserves better example.
Thanks a lot for this ❤️
I'll bookmark it for future reference :P
Привет из России. Спасибо за понятные и хорошие уроки это лучшие курсы для начинающих💗💗💗
Do you live in my head? How do you always know all subscriber's needs? Thank you!
I def needed this
Really Amaizing video , thank you 😎
Cool episode! Which one of dark themes plugin do you use?
Omg thanks very much ! ✨
As always Sir Philipp is here to save the day
thank you so much for this
Can you make video about usage of native ad as a up to date and how to use in jetpack compose?
Super awesome!!
is it acceptable to have the key be modified within the LaunchedEffect block?
Hello. I saw that people place derivedStateOf inside remember. Is that wrong?Because it cash and not calculate each run
Im stuck with EffectHandlersTheme not detect
So was I, but you can usually get the answers in the comments.
This is a response from @tetsuoshiva:
When you create a new Compose project, it creates a theme named "[ProjectName]Theme". Chances are the project was named "EffectHandlers", and "EffectHandlersTheme" is the theme that was created at project creation.
Just write your project name instead of "EffectHandlers", followed by "Theme".
Hey, just finished course about multimoduling. Have a question - when services are needed? For example, if there are any pros for moving api calls to service, if these are periodic calls made with workmanager? Thanks)
Workmanager is needed when you have work that needs to be done reliably, even when your app is closed or the device restarted. Not for user initiated network calls
very cool video thank you bro
In your MVVM News App, how to refresh the news list using swiprefershlayout listener or when call news list api from onresume override method?
I am new to MVVM architecture, please help me as i am calling the news list api in onresume but not in oncreate as i need to refresh the news list every time i came back to breakingnews fragment.
Hi Philipp, awesome video, thanks for the great content!
Just a question, how would you implement a snackbar call after navigation? when i perform an action, the app navigates up and need to show a snackbar, but i am just not being able to do it...
how would you do it?
Have it in a launched effect block in the screen you're navigating to if it should always show up or based on some kind of nav parameter
What you can also do is have a scope = rememberCoroutineScope and a scaffoldState = rememebreScaffoldState in your App() composable and a Scaffold. Your composables should expect a
showSnackbar: (String, SnackbarDuration) -> Unit
parameter, that you can call (for example when navigating up) like
showSnackbar ("Your snack message", SnackbarDuration.Short).
Your navigation composable should expect the same function parameter so you can just pass it on to your actual screen composables when creating the instances. In the end your Scaffold in App can look like this:
Scaffold(
..
state= scaffoldState
..
) {
..
YourNavigationComp(
navHost =...
showSnackbar = { message, duration ->
scope.launch {
scaffoldState.showSnackbar(message, duration)
}
})
}
With this solution you have a snackbarScope scoped to the App() so your snackbar is still visible during navigation and in the new screen. (Obviously if you need a snackbar scoped to your screen you can implement the scope and Scaffold there). Hope I could explain it well and could help.
Your question inspired me to write an article about about the topic in Medium, because I had this same struggle some time ago. I can not post the link here but added it to my youtube bio.
Great! So much useful!
On 7:02 you said that code in LaunchedEffect only once when screen composed for the first time. How another Event can happen in this case? E.g. it collects first event - ShowSnackbar and then Navigate event happens but you told that code executed only once
The launch effect block is executed once, so it subscribes to the flow once. But once a subscription is established the collect block will trigger with each event
@@PhilippLackner thank you
@PhilippLackner In the LaunchedEffectAnimation example. How can `counter` change? It’s just an Int parameter and is never assigned to. Would the example work the same if the first argument to LaunchedEffect were `true`? Great videos, by the way; I’m working my way through the original Compose series and have learned a lot.
Is it good to use derucedStateOf instead of rememberStateOf in all cases?
Adam geldi ADAM
at 3:00 you said its a terrible practise to directly call api inside composable. Can you please tell what is the best practise ?
Call it from a viewmodel / use case / repository
Sir Complete jetpack compose course.
Thankyou
what's the hotkey that you use at 15:28 to move the line up, through a brace, into onDispose scope?
oh, its shift+alt+up / down. looked it up
Wait, you never explained what EffectHandlersTheme is.
When you create a new Compose project, it creates a theme named "[ProjectName]Theme". Chances are the project was named "EffectHandlers", and "EffectHandlersTheme" is the theme that was created at project creation.
@@ArthurRousseau2 It has me stumped for an hour searching google, thank alot man.
@@ArthurRousseau2 Thanks! I started to come to the comments before googling stuff and I'm so happy for that.
What's the name of your android studio theme?
Philip
Xcode dark
I find scopes a really hard concept to get.
Not clear without examples
Love that content...
Happy it helps!
I'm so stupid, I still can't grasp what is it
Respect++ 🔥🚀
This side effect makes me think twice whet i should use this or maui csharpmarkup.
Compose makes it so much complicated especially in example.
Why not make normal oop. İnstead of frp
in order to conpansate for downside of functional programming,
they added remember state etc.
How to cover a hole
with another thing that also has a hole. Total bullshit..
형 너무 사랑해❤️❤️
Very cool lessons, please add Ukrainian subtitles.
Until video 9 in this playlist, I was more or less understanding the concept. After watching this one, I feel like I have totally lost the plot
Cool
Just example, therw is no practice :(
At 23:44 I noticed you're german
nice rewriting google guides
Thank you re baba Thank you
Always welcome