I wonder how does compose UI toolkit works internally? Does it have something similar to Flutter Ren...

# compose

[Ciprian Grigor]

I wonder how does compose UI toolkit works internally? Does it have something similar to Flutter RenderObject tree, heavy UI objects which are reused?

[Zach Klippenstein (he/him) [MOD]]

You might be interested in LayoutNode and OwnedLayer (and all the other files in this directory): https://cs.android.com/androidx/platform/frameworks/support/+/androidx-master-dev:compose/ui/ui/src/commonMain/kotlin/androidx/compose/ui/node/OwnedLayer.kt

[Ciprian Grigor]

Hard to get an answer from there

[jim]

If you want to understand how it works, you're going to need to dive into the code sooner or later. Zach is correct, we basically create trees of LayoutNodes, which are not widget instances (so unlike flutter) but are lightweight (like flutter) and are updated instead of recreated (which is why we have a compiler to help with tracking/applying those changes optimally).

[Zach Klippenstein (he/him) [MOD]]

For drawing, it uses Android’s RenderNode for drawing layers, which is also lighter-weight (and lower-level) than android views. However, on older android versions that don’t have RenderNodes, it falls back to Views for layers.

https://developer.android.com/reference/android/graphics/RenderNode

[Ciprian Grigor]

Thanks for clear explanation: kind of similar RenderNode = RenderObject, however is closer to android and android views can be intermixed with compose because of that

[Bsn Net]

what Android version is considered old?

[Zach Klippenstein (he/him) [MOD]]

Whichever version is before the first one where RenderNode was introduced