From data to UI: Compose phases - MAD Skills

Such a great explanation and interesting topic! Great video!!

Awesome content!

Given your explanation is it possible to visit each node in paralel?

Graphics make it very easy to follow the concepts ... very well done!

Very informative video! The layout algorithm of Compose seems to be quite similar to that of SwiftUI. 
It works as follows:
1. A parent view proposes a size for its child.
2. Based on that information, the child then chooses its own size and the parent must respect that choice.
3. The parent then positions the child in its 2D coordinate space.

Which begs the following question for me: 
When a composable measures its children in step 1, does the parent composable communicate a maximum size to the children? This information would be needed for example for a Text composable with multiple lines to know how tall it will be when its lines wrap at the maximum width of its parent.

Say that you’re German without saying that you’re German ;)

Nice explanation, thks :)

It sounds a lot like @flutter work. So why reinvent the wheel and not bring flutter into. As a 1st class tool

👋🏼🇨🇴🧔🏻👍🏼🤝🏻 Saludos desde Colombia.

Amazing video, I love to know how compose works deep down. Thanks a lot

That's why .. I love working on Android projects because when I don't understand something I'm sure I'll find a wonderful video like this that explain what I want .. thanks a lot

Really useful video ❤️! Especially the visualization of how the tree is recursively traversed! Keep ‘em coming!

And this is why we are asked about trees in coding interviews.

Well explained, Thanks Jolanda.

Thanks! Waiting for the next of these series! To the end of game;)

Please improve viewmodels. Give us the ability to preview composables that uses the viewModel lifecycle method

Thanks

Thank youuu <3

Awesome content 👏 😍

I need full course with the whole last updates, where to find the latest courses

How to find new updates and depricated codes in kotlin

Improve update support by separating the oem layer like miui one ui vivo from the system oartition and making system partition the aosp base for easy and make google to update the system partition easily like wut you did on dsu gsi and oem partition for oem to easily update while the product partition for gapps partition and vendor for device layer . Maybe retiring the dsu gsi test on developer option and actually allowing the google server to update the system.img the aosp base and the oem partition easily via settings like wut you did on dsu gsi via developers option might help everyone to experience latest os and as well as security