What is the purpose of removing the onClick from the button and passing a lambda instead? I mean it woukd still work on the passed count variable, right?
Thank you for the video! I have one question. Whether the composable depends upon a normal variable or the value of a state, it eventually both are normal variables. If we share the state itself, it would make sense that it is observing the state. How is it then reacting to the changes made in state values?
Actually, for composable, you do need .kt files to be made where you write your composable functions that will take space for sure. Now it depends on the structure of UI in both cases how much space it takes.
You will also have to include the dependancies for Compose, which would take some space and separate test framework dependancy as well for Compose if you need to test the compose UI.
This channel is a life saviour for aspiring Indian android developers ❤ Keep the good work going ❤
Previous video ki practice kar ke mai yaheen fasa tha... is hi video me answer mil gya 😄
Best explanation. Love from Nepal
Nice work Sir, Keep it cheezy always !
Very clear and to the point. Thank you
kash ap esi hi series flutter k liye bhi late
just amazinf explaination sir best content on youtube
Great, Great, Great teacher... Love from Pakistan.. Kindly add intermediate level canvas + drawing in this course. It will enhance the course.
Great example for state hoising
Sending Events Up is not clear to me.. if Multilevel Compose functions are used like One in another funtion.
Thanks for this playlist *#CheezyCode* 💜
value is not getting lost if rotate the screen and use only remember. it's working.
What is the purpose of removing the onClick from the button and passing a lambda instead?
I mean it woukd still work on the passed count variable, right?
Waiting for next video🙂
Thank you so much sir 😊🙏🫶
9:30 mast topic start hua h
Okay, So the remember is something like the static variable of composable scope, Right?
ek number
Thank you for the video!
I have one question. Whether the composable depends upon a normal variable or the value of a state, it eventually both are normal variables. If we share the state itself, it would make sense that it is observing the state. How is it then reacting to the changes made in state values?
Best Explanation ❤👏
Outro wala full song kaha milega sir?
Great Explanation :)
Is there any global state management thing like in react ?
well explained.
Best🙌🏻
bhai can't we just use mutable state as argument and parameter instead of the value, what are the consequences of that?
Thanks a Lot!
How do we achieve responsive of ui across all screens types using jetpack?
But in the last video you said we don't need to depends one another it doest not maintane sequence.
bought course on udemy and understanding those concepts on this channel 😂
Thank you
When compared to apps with XML, do apps with compose UI less in size?
Actually, for composable, you do need .kt files to be made where you write your composable functions that will take space for sure. Now it depends on the structure of UI in both cases how much space it takes.
You will also have to include the dependancies for Compose, which would take some space and separate test framework dependancy as well for Compose if you need to test the compose UI.
Sir HorizontalPager() lag karta hai .
any solution??
5:07 why do we use 'by' with remember{} then?
To interact with the state variable directly, without needing .value
Sir kya gpt-4 will replace fresher jobs in android developer?
In my Opinion, Not at current level of GPT-4. It is kinda noob at current state 🤣😂
👍👍
❤❤❤
❤
ek hi ❤ hai, kitni baar jeetoge?
Please share repo link.
is Unit Void?
Yes from Java perspective..but it is a type in Kotlin
🙏
Thank you 😊
Thank You