5 ms·
Thanks, it's astonishing how many teams make this mistake, simply putting some hungry library into the code to solve some story without thinking much further ab
by siva7 4y ago
Thanks, it's astonishing how many teams make this mistake, simply putting some hungry library into the code to solve some story without thinking much further about the overall implications
- robbyking 4y agoI don't know if it's still the case, but some third party libraries are required to run on launch. I worked on a an app where the Facebook login library took 600ms to load, and was required to run on launch.
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- saagarjha 4y agoI'm like 90% confident that it's their crash tracking or analytics library :P Edit: It's a framework from Salesforce called "ServiceCore". In case you were wondering it decided that it was necessary to request a list of all frameworks in a static constructor so it could find one that contains a certain class of theirs that does bundle-relative image loading. Pro tip, don't do this.
- __float 4y agoHow can you tell which framework it is?
- saagarjha 4y agoI pulled open the app and looked for frameworks with approximately 9 static initializers, one of which called into NSBundle. ServiceCore was the one that matched.
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]