Is there any performance Improvement in Compose 1....
# compose
s
Is there any performance Improvement in Compose 1.0? I just update my App on Play Store and I noticed slightly better performance. btw I am not using Lazy* Composable, the last time I used it had poor performance on older devices hopefully it improved as well 👍
here is little conversation about Lazy* performance improvements
r
@Shakil Karim We made a significant change to precompile part of the app earlier (as early as install time). Before this there were sometimes performance hits because of time spent JITing the app or running in interpreted mode
🙏 2
a
c
Oh sweet. I didn't realize there were any docs about that. 👌
s
@romainguy Hi. When does the Profile Installer take action? It is not clear from the documentation. When does Android studio is installing a release build to your device? Or when generate AppBundle file? Thanks.
☝️ 1
k
@Sergey Y. You can only install a release build on your device if you have access to the keystore of your app which is required for signing the release build. Any release build including the one you download from play store can take advantage of profile installer by doing AOT compilation of the code that is otherwise (on debug builds) done JIT.
c
You can sign a release build with a debug key. It just won't install in place if you have the app installed from play store for example.
k
@romainguy any recommendations on what should developers add to their profile file if they wish to? As in, how one can identify which components are qualifying candidates for AOT while rest can still be okay with JIT?