I was looking through my compose trace, and found that, after a recomposition, there’s a “traversal”...

# compose

[theapache64]

I was looking through my compose trace, and found that, after a recomposition, there’s a “traversal” calls which showing “LinearLayout -> FrameLayout -> ContentFrameLayout etc”.. Why’s this happening? Why am seeing views in recompose block when I don’t have any AndroidViews anywhere ? 🤔

[gildor]

Window frame and activity content, those are views

[gildor]

It looks that those are part of AndroidComposeView

[theapache64]

So when I access some activity, window thing from compose context, it goes through the AndroidComposeView? Is that what you’re saying?

[gildor]

Composable should draw somehow and Android is based on Activity which renders in window and uses View as root

[gildor]

So ComposeActivity uses AndroidComposeView to render composablew which itself is a part of Activity hierarchy

[theapache64]

understood 👍

[theapache64]

Any idea why all doFrame calls come under animation block ?

[gildor]

Nope

[gildor]

but just a guess, isn’t systrace just show different operations like this, so it shows that animation is happening during doFrame (which makes sense)

[theapache64]

all doFrames call has animation blocks under it. even if there’s no animation we’re doing from compass side.

[gildor]

Not an expert in systrace, but it looks that this what compose runtime reports to systrace: