(Partially huge) installation size of applications

de0u

gonzo255 Something that might be a factor: 64-bit binaries are bigger than 32-bit binaries.

gonzo255

de0u Both phones are 64bit arm. Apart from that only the size of pointers is doubled comparing 64 vs. 32bit architectures of the same type, resulting in a typical increase of a binary in the range of 5-10%.
Application/software is typically is so large in size because there are (media) assets packed into and/or dependencies as static linked libraries and whole frameworks compiled into.

gonzo255

Could someone confirm this posting theirs app installation size (without user data and caches) of typical apps?
Just to add some more i installed for tests:

(Facebook) Messenger: 376MB vs 173MB
Instagram: 551 MB vs. 230 MB
Booking.com: 363 MB vs 174 MB

Clark

gonzo255 my FB messenger app size is 396 MB.

Edit: never mind, minus user data it's 209 MB.

ILIKETRAINS

gonzo255 you might don't want to look at the GOS build no. but the App build no.

here some data points I can provide:
GOS P8 vs SAMSUNG S10+ (the only old device i have at hand)

Lemuroid:
309 MB / 29.27 MB
(tf!?)
Non-disclosed banking App:
139 MB / 79.90 MB
111 MB / 108 MB

Audiobook-App:
112 MB / 108 MB

Note: Samsung via PlayStore, GOS direct via sideloaded APK

gonzo255

Clark Could you specify the used (pixel-) phone and way of installation (in case of FB messenger play store / aurora)?

Clark

gonzo255 Pixel 7a, installed through Play Store.

matchboxbananasynergy

The difference in app sizes is a byproduct of AOT compilation of apps.

gonzo255

matchboxbananasynergy
I just verified that the app installation size is the same whether installed with aurora or play store.
Now - why do I, also using a Pixel 7a, like Clark, end up with an installation size of 378 MB for Facebook messenger an his is 209MB? - supposing he's running the very same, latest, version of GrapheneOS.
Could some more people post here theirs installation sizes (as written under 'Storage' after tapping 'Storage & cache' in 'App info' in the 'App size' field}?
I get that AOT compilation does some overhead, but why is it in the range of 10-150%? Why is no one else complaining about double installation sizes on the forum and nothing is mentioned in the FAQs?
I want to know if it's a strange bug only I do encounter or it's a common thing.

gonzo255

ILIKETRAINS in case of Lumuroid (1.16.1) i see an installation size of 44.43 MB on Pixel 7a GOS (Build 2024083100) (just the plain installation size, without userdata and caches). On some older LineageOS 14 device i get 30,17MB)
Could it be that your reported 309MB include user data?

ILIKETRAINS

gonzo255
the 309 MB are under App Size
(User _10MB, Cache _328MB, Total _648MB)
Build: 1.16.0
GOS: up to date

gonzo255

ILIKETRAINS ahhh... i think that could, possibly, maybe be some emulation cores (necessary to emulate specific systems) added after the initial installation.

ILIKETRAINS

gonzo255 would be also my theory - if the app never had network permission.
I just took a look at "apk mirror" (easiest way to compare builds, imo) - it seems there are the following apk's for build 1.16.0:
apk over 160mb (no dpi pre-set),
around 90 MB (160 - 640 dpi)
around 40 MB (120 - 640 dpi)
So it might make a difference which pre-set for dpi is loaded/chosen