Very slow perfomance about compose-samples

[NurseyitTursunkulov]

Android team as always weak, compared with iOS

[daniel-micic]

same thing happening in stable release. why is this not opened again ?

[iRYO400]

It's still same for today (11.14.2020)
Tested on Huawei P20 Lite

[muhammadalkady]

It's still same for today

[jgavazzisp]

It seems to happen only on the very first screen loaded.

[mahdisml]

So true ! It happen only in first startup !

It seems to happen only on the very first screen loaded.

@nickbutcher please open this thread :)

[nickbutcher]

Jetpack Compose is currently in Developer Preview and has not been optimised for performance. Closing this issue.

[anlexN]

just preview my background, it costs me 47s, oh my god. i am very very angry.

[hamthelegend]

My debug version is also slow, but the release build (with minify enabled) is super performant. Geez people. Why are you so angry. lol. Just say your problems in a civilized fashion.

[muhammadalkady]

@hamthelegend Jetpack compose still runs in interpreted mode in release the first few times. So it is slow at first which is important for UX.

[hamthelegend]

AFAIK, the release build does not @muhammadalkady. Correct me if I'm wrong

[muhammadalkady]

@hamthelegend even in release mode still runs in interpreted mode.
https://developer.android.com/jetpack/compose/performance#use-baseline

Compose is distributed as a library, instead of being part of the Android platform. This approach lets us update Compose frequently and support older Android versions. However, distributing Compose as a library imposes a cost. Android platform code is already compiled and installed on the device. Libraries, on the other hand, need to be loaded when the app launches, and interpreted just-in-time when the functionality is needed. This can slow the app on startup, and whenever it uses a library feature for the first time.