Android Gradle Plugin

There's a baseline profile text file, which an application or a library could declare and include it in their AAR. And so these files have essentially a set of all call them rules where they indicate this method is hot. This one is important for startup, but not afterwards and stuff like that. When the APK gets pushed up to the play store or installed on device, that ends up getting put into one or both of two buckets. So if you're using compose for instance, this is happening for you,. It will then look for the profile in the APK. If it exists, then it'll use it to inject that profile and provide it to art when the application is first