8 ms·

How iOS 15 makes apps launch faster

154 points by jshchnz 5y ago

br3n0_m4rqu3s09 5y ago
:(
nvr219 5y ago
Kind-of related because this article is on medium... Any downside to me blocking `||accounts.google.com/gsi/iframe/select` via ublock origin? Will this break my use of google drive or search engine? I hope not because I'm doing it anyway. Medium.com makes me barf. Which is sad because it hosts some great content.
- edgeform 5y ago
  It appears to be related to sign-in flow[1], but may not affect signing in via Google.com or other Google-hosted services directly. It's the API for "Sign in with Google", far as I can tell here. [1]: https://developers.google.com/identity/gsi/web https://developers.google.com/identity/gsi/web
  - nvr219 5y ago
    Thanks
- cyral 5y ago
  The Sign in with Google dialog even shows for me, a logged in user..
- the_duke 5y ago
  For medium I recommend just blocking Javascript. No signup popups, fast loads.
- tech234a 5y ago
  If you go to https://myaccount.google.com/permissions https://myaccount.google.com/permissions, you can turn off "Google Account sign-in prompts" on each of your Google Accounts and then you won't see any more of those prompts. Don't know if Facebook has a similar option for their accounts though; I've seen a similar sign-in prompt elsewhere for Facebook.
jtbayly 5y ago
But only if you make your app incompatible with all older iOS versions? Seems to me like not many people will benefit from this.m for some time to come.
- sond813 5y ago
  There’s also a linker flag that lets you use this format on older OS versions. It seems to work (I tested as far back as iOS 13.4.1) but couldn’t find any documentation to guarantee it won’t cause issues https://developer.apple.com/forums/thread/683596 https://developer.apple.com/forums/thread/683596
- munk-a 5y ago
  As someone with a device locked on iOS 10 this makes me very happy. I have a desktop computer I bought in 2008 which is running Windows 10 and happy as a clam - and yet all my apple devices from before 2018 are essentially now bricks.
  - Shadonototro 5y ago
    iOS 15 supports up to iPhone 6s wich was released in 2015 Windows 11 supports PCs with processors up to Intel Gen 8, wich was released in late 2017
    - hermitdev 5y ago
      I'm currently running Windows 11 preview on an i7 3970, circa 2012... It might not be "supported" at launch, but it works currently.
  - jackson1442 5y ago
    What model? iPhone 6S was released in 2015 and will be able to run iOS 15.
    - mixmastamyk 5y ago
      Also Intel PCs haven’t changed a fraction as fast as the iPhone did in last decade.
can16358p 5y ago
What about submitting Bitcode when uploading to App Store Connect? Would it take advantage of the change and build an optimized binary for iOS 15 while still supporting the old way on pre-iOS 15 and deliver the appropriate binary upon download?
- deleted 5y ago
  [deleted]
- sond813 5y ago
  The mach-o format supports a “fat binary” that contains multiple architectures and then the App Store can only deliver one of those architectures to a particular device. Bitcode lets Apple recompile a different architecture slice using this format. However, since this change is unrelated to the architecture it can’t take advantage of this format.
dwighttk 5y ago
I hope this works in my old iPad… I’ve been noticing quite a bit of slowness these days
- cheschire 5y ago
  Not sure which model you have but it looks like they’re supporting the same models as iPadOS 13 and 14 https://en.m.wikipedia.org/wiki/IPadOS_15#Supported_devices https://en.m.wikipedia.org/wiki/IPadOS_15#Supported_devices
plorkyeran 5y ago
Things like this make me wish that we could submit multiple builds to the app store with different deployment targets and have it install the highest supported one. They've made a few of these runtime improvements over the last few years that could make apps faster and smaller, but in practice very few of the apps I have installed take advantage of them because they prefer to maintain compatibility with older versions instead.
- colejohnson66 5y ago
  Isn’t that the idea with “bit code”? Basically, Apple keeps the LLVM IR (of sorts) and optimizes it on their end (and removes unneeded image assets (such as @2x on an @3x device)). So the build your device downloads is highly optimized specifically for your device model. Or do you mean something else?
  - lanza 5y ago
    This would only support optimizing for different architectures. Your code is already compiled from Swift -> IR and thus these features would not be part of the IR.
    - inkyoto 5y ago
      Architecture specific («post-compile» time pass) and chained fixups (link time pass) optimisations are orthogonal, and both can take place. Since a) Bitcode IR is, essentially, an object file; b) the destination platform version is known at the post-processing (i.e. download) time, it is possible to also optimise the executable binary format to make us of whatever enhacements are available, too.
  - saagarjha 5y ago
    Bitcode does not do this, unfortunately.
  - plorkyeran 5y ago
    There isn't much evidence that Apple has ever used bitcode for anything other than making existing watchOS apps run on the new arm64_32 architecture. It's required for app thinning (where they only install the architecture needed for the actual device rather than all of them), but if that's not just an arbitrary requirement to get people to enable bitcode it's unclear what it's being used for. I don't know if bitcode could be used to recompile your app with a higher deployment target and have useful effects, but it isn't being done in practice.

154 points by jshchnz 5y ago

Kind-of related because this article is on medium... Any downside to me blocking `||accounts.google.com/gsi/iframe/select` via ublock origin? Will this break my use of google drive or search engine? I hope not because I'm doing it anyway. Medium.com makes me barf. Which is sad because it hosts some great content.

edgeform 5y ago
It appears to be related to sign-in flow[1], but may not affect signing in via Google.com or other Google-hosted services directly. It's the API for "Sign in with Google", far as I can tell here. [1]: https://developers.google.com/identity/gsi/web https://developers.google.com/identity/gsi/web
- nvr219 5y ago
  Thanks
cyral 5y ago
The Sign in with Google dialog even shows for me, a logged in user..
the_duke 5y ago
For medium I recommend just blocking Javascript. No signup popups, fast loads.
tech234a 5y ago
If you go to https://myaccount.google.com/permissions https://myaccount.google.com/permissions, you can turn off "Google Account sign-in prompts" on each of your Google Accounts and then you won't see any more of those prompts. Don't know if Facebook has a similar option for their accounts though; I've seen a similar sign-in prompt elsewhere for Facebook.

jtbayly 5y ago

But only if you make your app incompatible with all older iOS versions? Seems to me like not many people will benefit from this.m for some time to come.

sond813 5y ago
There’s also a linker flag that lets you use this format on older OS versions. It seems to work (I tested as far back as iOS 13.4.1) but couldn’t find any documentation to guarantee it won’t cause issues https://developer.apple.com/forums/thread/683596 https://developer.apple.com/forums/thread/683596
munk-a 5y ago
As someone with a device locked on iOS 10 this makes me very happy. I have a desktop computer I bought in 2008 which is running Windows 10 and happy as a clam - and yet all my apple devices from before 2018 are essentially now bricks.
- Shadonototro 5y ago
  iOS 15 supports up to iPhone 6s wich was released in 2015 Windows 11 supports PCs with processors up to Intel Gen 8, wich was released in late 2017
  - hermitdev 5y ago
    I'm currently running Windows 11 preview on an i7 3970, circa 2012... It might not be "supported" at launch, but it works currently.
- jackson1442 5y ago
  What model? iPhone 6S was released in 2015 and will be able to run iOS 15.
  - mixmastamyk 5y ago
    Also Intel PCs haven’t changed a fraction as fast as the iPhone did in last decade.

can16358p 5y ago

What about submitting Bitcode when uploading to App Store Connect? Would it take advantage of the change and build an optimized binary for iOS 15 while still supporting the old way on pre-iOS 15 and deliver the appropriate binary upon download?

deleted 5y ago
[deleted]
sond813 5y ago
The mach-o format supports a “fat binary” that contains multiple architectures and then the App Store can only deliver one of those architectures to a particular device. Bitcode lets Apple recompile a different architecture slice using this format. However, since this change is unrelated to the architecture it can’t take advantage of this format.

dwighttk 5y ago

I hope this works in my old iPad… I’ve been noticing quite a bit of slowness these days

cheschire 5y ago
Not sure which model you have but it looks like they’re supporting the same models as iPadOS 13 and 14 https://en.m.wikipedia.org/wiki/IPadOS_15#Supported_devices https://en.m.wikipedia.org/wiki/IPadOS_15#Supported_devices

plorkyeran 5y ago

Things like this make me wish that we could submit multiple builds to the app store with different deployment targets and have it install the highest supported one. They've made a few of these runtime improvements over the last few years that could make apps faster and smaller, but in practice very few of the apps I have installed take advantage of them because they prefer to maintain compatibility with older versions instead.

colejohnson66 5y ago
Isn’t that the idea with “bit code”? Basically, Apple keeps the LLVM IR (of sorts) and optimizes it on their end (and removes unneeded image assets (such as @2x on an @3x device)). So the build your device downloads is highly optimized specifically for your device model. Or do you mean something else?
- lanza 5y ago
  This would only support optimizing for different architectures. Your code is already compiled from Swift -> IR and thus these features would not be part of the IR.
  - inkyoto 5y ago
    Architecture specific («post-compile» time pass) and chained fixups (link time pass) optimisations are orthogonal, and both can take place. Since a) Bitcode IR is, essentially, an object file; b) the destination platform version is known at the post-processing (i.e. download) time, it is possible to also optimise the executable binary format to make us of whatever enhacements are available, too.
- saagarjha 5y ago
  Bitcode does not do this, unfortunately.
- plorkyeran 5y ago
  There isn't much evidence that Apple has ever used bitcode for anything other than making existing watchOS apps run on the new arm64_32 architecture. It's required for app thinning (where they only install the architecture needed for the actual device rather than all of them), but if that's not just an arbitrary requirement to get people to enable bitcode it's unclear what it's being used for. I don't know if bitcode could be used to recompile your app with a higher deployment target and have useful effects, but it isn't being done in practice.