Topic was automatically imported from the old Question2Answer platform.
Asked By
i_love_godot
Ok, so I have been reading this article about APK size optimization, but that doesn’t reduce the APK that much when using export templates that I compile from source VS the default ones. I even tried this optimization method… but I’m not seeing anywhere near the size savings that that person achieved.
Even with a really basic demo project, that doesn’t contain much, I’m barely getting the APK under 20MB. Is this the new normal? Is that just how big the Godot engine is?
The size itself isn’t really a deal breaker, but I do like the idea of only including the modules I need. Would it speed up the app startup time too? Basic apps tested on fairly modern Android devices take several seconds to reach first scene. Presumably because the engine is loading a lot of things I won’t use. Maybe that’s a misguided optimization attempt, I don’t know.
If anyone has compiled their own export templates and has some tips for optimizations, please feel free to share
You should export one APK per architecture supported by Android (ARMv7, ARMv8, x86) then upload them using Google Play’s multiple APK support. x86 is optional, but ARMv7 and ARMv8 (64-bit ARM) will be required starting from August 2019. To do so, create several export presets, each of them having only one architecture checked (the export process will strip unused libraries from the APK).
This will make each APK much smaller as it will only contain the native library required by the user’s device.