Subscribe for the latest → goo.gle/AndroidDevs

I just wanna learn even more now- it looks so cool o.O

Awesome!!! Thanks for the info ❤

Muchas gracias por la información, que nos proporcionan es de gran ayuda. Un gran abrazo a todo el equipo de android 🤗

Thanks much for this series! I'd like to make one caveat on the _"No more XML needed"_ comment. XML isn't the issue. It's how Android Studio propagates XML details, with massively cascading properties that end up conflicting that is the problem. Here's hoping that didn't jump over into Compose. Thanks again for the tutorials!

Android Developers never fail to impress

Great video. I have a question 5:43 .How does onAnswerSelected relate to or triggered with the onClick of the RadioButton?

Thank you man for sharing this stuff

this is 🔥🔥

Un video maravilloso, valioso, importante, exitoso y útil, bendiga su esfuerzo y que Dios lo recompense con la mejor recompensa, mis saludos, mi cariño y mi gran aprecio.🖒❤🍀🖒

Awesome for sure! Is Answer a built in class or user defined? I mean upon toggling a radio button, is the object updated is an instance of Answer?

Very helpful

Add display resolution change like 720p 1080p toggle for support devices and allow all windows to be resizable and free formed by default

LESS CODE : COMPOSTABLE FUNCTIONS - MAD SKILLS

1:06 That seems counterintuitive that answers,forEach { // ... } will add SurveryAnswer composables to parent composable - Column Because answers,forEach { // ... } returns Unit It makes more sense to use answers,map { // ... } but it won't work, because SurveryAnswer composable returns Unit type It would be great if you would make series about Jetpack Compose internal implementation so we could understand why it works.

I can't wait to put my hands on this baby !!!!

In 6:18, I think the "selectedAnswer" should be var instead of val, right?

Summary: 1. Composable functions are immutable. You can not get any reference to them to change their state later. 2. They should be fast and free of any side effects. 3. Composables are idempotent. 4. They transform state into Ui. That means they are entirely dependent on the properties they are passed. 5. Recomposition happens when a composable is called with a new value of arguments. 6. But it can also happen when internal state in a function changes. 7. MutableState - any changes in the state of this variable will automatically tell its composable to schedule the recomposition. 8. remember - guarantees that the value is not reset when the composable is reset. 9. rememberSaveable - guarantees that the value is not reset when the config changes. 10. In order to remain side-effect free, composable functions should not write to any variable from outside of their scope. 11. Composables can run in parallel. They can run in any order. 12. Recomposition re-draws only that part of UI where state is changed. It skips as much as possible. 13. Recomposition is optimistic. It expects to complete the drawing before the next state change. But even if the next state change happens early, it cancels the current drawing. 14. In cases such as animation, composables might run frequently.

The MutableState's auto-re-render mechanic is very interesting, I wonder how they implement it. Where can I read more on this without a deep dive of the source code please anyone?

bm - 2:15

412th...Thanks Chris

😎😎

Jetpack is very promising

Compose makes development simple but the performance is not helping. It doesn't give me the native feel.

This is basically React and virtual dom

Agregauncomentrio

I want to like this video, but the current like count 444 looks beautiful enough for me not to like this video 😆

i m 678th liker