Drawn out: How Android renders (Google I/O '18)

[@llothar68]

And all of this complexity in 16ms. This blows my mind away. We came really a long way since i did it by poking into my C64 memory buffer.

[@typingcat]

16 ms? But I want it now....

[@warrencampbell6814]

I'm pretty sure we can (and should) do this in less then 16ms. Especially for applications where latency is more noticeable and strongly avoided (i.e. VR/AR/Gaming).

[@blanamaxima]

everything flies with a big enaugh engine

[@pandyasankalp]

Okay ,probably one of the few videos on the KZbin which I do not have to watch at 1.5X.

[@oanhle-em3qv]

From Google I/O 2018, it's very little Frame and Graphics sessions. I think that should have more and more these sessions.

[@DeLL116]

Ahhh... The "good ol' days"

[@ajaykumarsahoo6008]

Nice explanation. Are the slides available somewhere ?

[@balajim7801]

How does the browser rendering differ from native rendering? At what point do rendering calls merge towards their way to the monitor? Is it possible for browser rendering to merge at DisplayList?

[@berbap7478]

26:35 is this sync issue really fixed in android?

[@FlexoShootFlexo]

Romain Guy is my spirit animal

[@llothar68]

Please .... please .... i want someone write an expert level book about all this stuff. I know the first part of it because thats how it was done since the days of Motif in 1992. But the second half with GPU acceleration needs much more exposure. I'm buying technical books and many others too. So a new "Petzold" for Android Internals.

[@lpskumar22]

where is application code and app name, he referred at 34:10

[@danielbonatti3451]

Its "Grafika", on Github: github.com/google/grafika

[@GotUpLateWithMoon]

Why does invlidate() of a child needs to bubble up to the root view? Why traversal needs to happen exhaustively/top-down instead of just merging the changed part and the unchanged part? which doesn't sounds like need the root view to be involved

[@DeLL116]

If my memory serves me, it's because the child may have changed its bounds. If that is the case, parents of that child may need to resize and that might cascade down the entire child/parent tree.

[@nwxxzchen3105]

What's the limits of the surface view compare to texture view? Why surface view cannot be sanwiched?

[@nwxxzchen3105]

Why use textureView instead of surfaceview in the older version of android?

[@NavalKishoreBarthwal]

From where can we get the slides??

[@kollerke8943]

are you get the slides?

[@alexandrprodan8794]

Has anything changed in 2024, If someone knows a videos or article with updates please share it with us.

[@NghiNguyenVan]

This is a simple case when HWUI and GPU don't involve rendering process directly like play a game. Anyway, those things almost seem to be said before. I wish something news were Vulkan and HWC 2.0 or how HWC compose layers :)

[@benidobre]

Romain guy is his name or is he a guy from Romania?

[@KangJangkrik]

Both, coincidentally

[@sebastienleclerc8772]

@@KangJangkrik Nah, he's French.

[@KangJangkrik]

@@sebastienleclerc8772 How do you know?