I find "ensuring app loads fast" to be absolutely hilarious, here. What has to be done to help a mail app load fast?
And, snarkily, can they do this for the web page? On my decent connection right now, loading a new tab to gmail takes about 3 seconds to visibly load. Another few seconds to get so that I can interact with it. Is kind of hilarious to see how long it takes to load the compose window if I press "c" as soon as I see any of the app has loaded.
Right, I know what sort of things happen in that process. And to be fair, I'm mainly poking fun at how bad the web page has become.
I do feel that this bloat is, far and away, the worst offender when it comes to why things feel slower nowadays. The application just flat out does way more than most people assume it can. Which means it almost certainly has way more capabilities than it needs for many of us.
Would be neat to see a metric on "how much of the code is never loaded" in typical use. Akin to some game medals of "played more than x% of players."
AOT is unique because you want to compile it with all the capabilities your device has, so there still has to be some complication done, especially when you have processors that have brand new instructions to make operations significantly more efficient.
That's not the approach they're referring to, iOS doesn't support that. They're referring to delivering the compiled native code as part of the app package.
Frameworks 150MB
Assets for all screen resolutions 50MB
Google Meet/Chat/etc 100MB
AI models 25MB