A modern programming language that makes developers happier.

kotlinlang

Hi everyone. I'm really exited about jetpack compose. I know this is just a dev preview but I built "Jetnews" sample application and there is some lags when screen changes, I guess there planned some performance improvements. Also, I wanted to is there any solution for navigation eg. handling backpress etc?

it's doing a few silly things like decoding bitmaps on the UI thread and not caching them as you navigate around :slightly_smiling_face:

<@UJBKXD0HH> you mentioned coroutines in your talk.  Can I take that to mean you intend to have a first party solution for async resource loading ala Picasso?  :crossed_fingers:

thank you Adam, makes sense :slightly_smiling_face:

Maybe at some point; first I want to make sure we have all of the correct hooks in place such that you could integrate Picasso, Glide, Coil or whatever with their existing caching systems intact :slightly_smiling_face:

<@UJBKXD0HH> I was looking at the systrace and there is a big animation block on every frame even if no animations are running. I was curious why would it be there.

Probably Compose doing a lot of work on a frame animation callback pulse since it's guaranteed to run before the next frame

So the re-composition is driven by the animation callback?

<@UJBKXD0HH> I figured it out turns out all the compose traces to not show up on `systrace` but they all show up nicely on the `perfetto-traces` that get recorded by the device, and it seems that the `Compose observers` get run by animation callback.  (Edit: turns out they do show up but they are in the app space, and i was taking the trace wrong).

That work is unlikely to remain there long term, please pardon the dust :slightly_smiling_face:

I was curious because the draw calls seem to be on par with the current view system which is to be expected since it uses the same rendering. But there was this animation block on all the traces that took big portions of the frame time.