4 ms·

It looks like all of these apps had a notable bump in size at about the same time. I'm wondering what happened at that point to cause this.

• chmpgne 9y ago
  Swift still doesn’t have ABI comparability yet, so that could definitely explain some of the bump
• izacus 9y ago
  Probably Apple lifting size restriction.
  • mahyarm 9y ago
    It not approaching the 4GB limits, its an addition of 100MB.
  • eridius 9y ago
    It looks like Facebook was already over 100MB when the bump happened, so it must have been something else.
• valuearb 9y ago
  One effect two years ago was 3x retina images for first iPhone 6 Plus, roughly doubled size of all asset catalogs. With app slicing the 3x aren't usually downloaded to most devices, but that's not clear to customers.
  • ocrickard 9y ago
    Around the same time was the 64-bit requirement for app updates. This resulted in a dual-slice fat binary. Began being enforced in June 2015 I think, so about 2 years ago.
    • eridius 9y ago
      App Thinning handles that issue too.
      • valuearb 9y ago
        It dies but store lists full fat binary size.
• andrethegiant 9y ago
  Probably due to the release of Xcode 8.3, which creates binaries 3x the size of those created by Xcode 8.2.1. https://news.ycombinator.com/item?id=13991851 https://news.ycombinator.com/item?id=13991851
  • plorkyeran 9y ago
    That bug was fixed one week later in Xcode 8.3.1 and the app store rejects apps built with 8.3.0.