Great video, hovewer your explanation of triStateCheckbox is not compliant to material3 standard. The material3 guidelines state that: "Checkboxes can have a parent-child relationship with other checkboxes. > When the parent checkbox is checked, all child checkboxes are checked > If a parent checkbox is unchecked, all child checkboxes are unchecked > If some, but not all, child checkboxes are checked, the parent checkbox becomes an indeterminate checkbox" Thus, the indefinite state is not set as the initial state, but rather is fully dependent on the state of its children.
This video just came in very much on time because I've just started to convert my very very old Android apps from Java to Kotlin and I'm looking at things like JetPack Compose and this tutorial for Material3 is something that can really help me out! Thanks for the great video!
To remove the ripple effect from the row and have it only inside the radio button or checkbox, 1. In the row clickable modifier set the indication to null. 2. Create a MutableInteractionSource. 3. Pass the MutableInteractionSource to both the row and the radioButton or checkbox.
Bro, you make very cool and helpful videos, thanks. I would like to see the implementation in design patterns using Kotlin. For example, the decorator pattern can be implemented through Interface Delegation. and so on.
recaps at the end of videos are really a good way to help us memorize the material covered in the video, but it would be great if you did it for 1 to 2 minute not less
I think there could be some rare cases where it is important to require the user to make an unbiased choice (so that they pay enough attention to their options and don't fall for the "default option trap"). Would this justify not having a radio button selected by default, or should we use some other UX component instead?
Bro i need to track user location using geofencing in background so that when he leaves particular loaction another service should eb triggered and then another i kind of need them to get triggered in a chained reaction manner and all of this should be done in background even when the appi snot opened please tell em how to do this
Great video, hovewer your explanation of triStateCheckbox is not compliant to material3 standard. The material3 guidelines state that:
"Checkboxes can have a parent-child relationship with other checkboxes.
> When the parent checkbox is checked, all child checkboxes are checked
> If a parent checkbox is unchecked, all child checkboxes are unchecked
> If some, but not all, child checkboxes are checked, the parent checkbox becomes an indeterminate checkbox"
Thus, the indefinite state is not set as the initial state, but rather is fully dependent on the state of its children.
This video just came in very much on time because I've just started to convert my very very old Android apps from Java to Kotlin and I'm looking at things like JetPack Compose and this tutorial for Material3 is something that can really help me out! Thanks for the great video!
That was great, Philipp.
because you explained every Component so patiently and in complete detail.😇
To remove the ripple effect from the row and have it only inside the radio button or checkbox,
1. In the row clickable modifier set the indication to null.
2. Create a MutableInteractionSource.
3. Pass the MutableInteractionSource to both the row and the radioButton or checkbox.
Need compose desktop videos 🙏
Bro, you make very cool and helpful videos, thanks. I would like to see the implementation in design patterns using Kotlin. For example, the decorator pattern can be implemented through Interface Delegation. and so on.
recaps at the end of videos are really a good way to help us memorize the material covered in the video, but it would be great if you did it for 1 to 2 minute not less
thank you bro.
Thanks for your videos!
Great video like everyone else! Could you tell me which android studio theme you are using, please?
I think there could be some rare cases where it is important to require the user to make an unbiased choice (so that they pay enough attention to their options and don't fall for the "default option trap"). Would this justify not having a radio button selected by default, or should we use some other UX component instead?
I hope to make a video about MaterialTheme object in the material3 and their colours
Nice video as always! Also, will you cover menus in one of the next videos?
How to add expandable on checkboxes
thanks.
Bro i need to track user location using geofencing in background so that when he leaves particular loaction another service should eb triggered and then another i kind of need them to get triggered in a chained reaction manner and all of this should be done in background even when the appi snot opened please tell em how to do this
1