|
|
|
|
|
by jasode
820 days ago
|
|
>, but optimising 500MB to 300MB would be very impactful to installation rate. [...] It is a very significant portion of the population who are borderline out of storage all the time. I work quite closely to this sort of stuff on a regular basis. Does Apple send telemetry information back to developers about failed app installs due to users' device being out of space? I don't have a current Apple Developer account to test this but the documentation doesn't have any obvious statistic concerning failed installs: https://developer.apple.com/help/app-store-connect/view-app-.... EDIT reply to: >I don't think there's any special permissions required to get free disk space, so presumably he's getting it via telemetry from his app. I was thinking of new users who didn't have the app at all. E.g. hypothetical... "We're a brand new YC tech startup. Our app is 500 MB. This bloated size prevents 20% of potential new users from installing the app." <-- Does Apple provide enough stats to make that type of confident correlation? |
|
For all I complain about OKR’s, this is a super simple one for LinkedIn to understand: Every MB your app takes up can probably be shown to decrease user stickiness by some percentage. Fix it!
Ah who am I kidding, they’ll probably switch to moving the assets out of the app bundle and making them live-download on first run and stored in the Caches folder somewhere, which will make the app “smaller”. Problem solved on their end, app-size OKR accomplished. The fact that it makes the app slower due to asset fetching is next quarter’s problem.