Has anyone noticed that Compose (debug not release) is running significantly slower on Android 14 vs Android 13?

Did you test exact same compose versions etc in a real Android 13 and a real Android 14 device? Otherwise it could be compose version, it could be the emulator being slower, it could be much more. With that said reading your message I do feel like in the past months my debug app has been a bit more choppy, but I haven’t really looked into it.

Yup, same versions, both on Pixel 7s

Interesting, I don’t know how you’d explore this further. Doing benchmarks on the device perhaps? But then you’d have to compare it with the same device on Android 13 which would be quite hard for an individual perhaps

I have two Pixel 7s one with 13 and one with 14 so it shouldn't be too bad.

Oh you do have the right now, that’s quite convenient 😅 I thought maybe you were just on 13, then upgraded (on the pixel 7s) and then tested again.

Luckily not yet 😅

@romainguy... any thoughts?

Bumping this because my debug builds have slowed to a crawl on Android 14. Anyone else seeing this?

is that why debug has been sooooo bad? I'm in Android 14 QPR 2 or w/e its called.

I imagine that's it. I've been trying to profile to see what's going on but the profiler and layout inspector aren't working 😐

@Ben Trengrove [G]?

the same comparison holds true for older API:s as well in my experience; feels like a release build after youve toyed with it for a bit, even if its a first-install debug build.

There's a marked difference when I test this on a Pixel 7 running Android 14 and a Pixel 7 running Android 13

I’m seeing this as well, but I assumed it was just me. Also Pixel 7a (Android 14) and still using fragments.