Good news: I don't know if this has already been p...

# compose-ios

[darkmoon_uk]

Good news: I don't know if this has already been pointed out, but it appears to me that bumping Compose from 1.2.1 to 1.3.0-rc01 has dramatically improved performance on iOS 🎉

On 1.2.1 we had some test screens that showcased a lot of typography styles, and another that displayed a large colour palette in a LazyGrid ; these were both very slow to initially render, in the order of 2-5 seconds, and subsequent scrolling was choppy. Now everything is on a par with Android i.e. instantaneous, smooth.

(Yes, I'm talking about Release build in both cases - being aware of the general _Debug_/_Release_ performance disparity in Compose).

Can anyone confirm these improvements and whether they're expected? Nice work [JB]! ❤️K

[Norbi]

it would be interesting to know what caused such huge performance improvement...

[darkmoon_uk]

Yes, and to have it corroborated - anyone else with a Compose/iOS project out there, that they can spin up for comparison?

[Michael Paus]

Is this also true for the latest 1.3.0-beta04-dev903? (Why are we back at beta from rc anyway?) These version jumps are confusing me.

[Oleksandr Karpovich [JB]]

Hi!
First of all, I’m sorry for the confusion with versions (1.3.0-beta04-dev903 had to be named 1.3.0-rc02-dev903. The naming adjustment relies on a manual action, and we missed it last itme).

Since 1.2.1, we haven’t made any intentional work to improve the performance. We suspect some improvements could’ve originated from the upstream after rebasing.

We’d be glad to dig into it a little bit. @darkmoon_uk If you have your test somewhere published, we’d take a look into it

[Landry Norris]

I believe Google started work on the internals of Modifiers that is supposed to improve performance a lot. They said this will be a multi-year change, but Modifiers already seem to have less of an impact on performance. The first steps came in with 1.3.0