Optimizing Android build size

Questions
#1

Hello everyone!

I have a question about optimizing Android application bundle builds for size, because currently my .aab file is 308 MB in size.

I added 150 images in a simple test project which just shows them one after the other on a button press. The complete images folder takes up 41 MB on disk and the images are packed into 15 Atlases. The generated build report claims that textures take up 27 MB of the build and that those 27 MB are 97 % of the total build size.

I made sure that it is not a debug build and that texture compression is enabled:

image

I don’t understand the large build filesize and any tips on what I might be missing in the settings would be greatly appreciated.

Thanks in advance for any input on this matter and best regards,
Patrick

#2

Can you share the report here?

#3

Hello @britzl!

Yes of course, here is a ZIP file with the report files: defold-build-report-armv7-android.zip (476.8 KB)

Thanks for having a look and best regards,
Patrick

#4

Sorry for the delay. The report doesn’t show anything out of the ordinary. What if you unzip the .aab file? Can you check what is taking up all of the extra space?

#5

Hello @britzl!

The file base/assets/game.arcd takes up 302 MB, the complete unzippled .aab file is 305 MB on disk.

Again thanks for your help and best regards,
Patrick

#6

That’s strange. @AGulev any ideas? @Patrick_K would you be able to share the project with me?

#7

No, I don’t know. Build reports look just fine.