You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting with v1.2.0, APKs increased in size by factor 30 – which is quite a lot. I assume this is mostly due to the native libraries being added for all the different architectures.
Would it be possible to "slim down" a bit?
For example, is the 6M raw soundfile (an MP3 I assume) really needed in the package (res/raw/song)? And as Android devices using MIPS architecture are not that wide-spread, maybe have an APK without this architecture, saving another ~10M? A "minimal" APK could even only ship with armeabi+x86, which should work on all ARM and X86 devices – and that APK would shrink down to ~11..12M (still factor 10 to what it was before v1.2.0). If the "full APK" is available separately, everyone is free to chose.
The text was updated successfully, but these errors were encountered:
@hikikomoriphoenix no comment at all? I've just checked again: without that song, size goes down to 30M. Leaving out mips as well, to 25M (one third). ARM only would be 15M (less than half of the original size).
Starting with v1.2.0, APKs increased in size by factor 30 – which is quite a lot. I assume this is mostly due to the native libraries being added for all the different architectures.
Would it be possible to "slim down" a bit?
For example, is the 6M raw soundfile (an MP3 I assume) really needed in the package (
res/raw/song
)? And as Android devices using MIPS architecture are not that wide-spread, maybe have an APK without this architecture, saving another ~10M? A "minimal" APK could even only ship with armeabi+x86, which should work on all ARM and X86 devices – and that APK would shrink down to ~11..12M (still factor 10 to what it was before v1.2.0). If the "full APK" is available separately, everyone is free to chose.The text was updated successfully, but these errors were encountered: