Yes, I tested in similar conditions, ofc.
New tests with empty projects.
Unity version 2019.4.0f1
Defold 1.2.170
Pls check projects to make sure I removed everything I could.
In Unity, I use Stripping Level High which is pretty dangerous and often breaks bundle. In Defold I did two builds, one without AppManifest at all, and another one with manifest that cuts off Physics modules and Record module.
Android
AAB size is not the same count of megabytes that will be delivered to the end-user. Pls, check apk sizes - it’s closer to size end-user will download.
Unity build Android AAB (32 and 64 bit) - 11 Mb
Defold Build Android AAB (32 and 64 bit) - 3.3Mb
Defold with AppManifest Build Android AAB (32 and 64 bit) - 2.7Mb
Unity Android apk 32 bit - 5.7 Mb
Defold Android apk 32 bit - 1.6 Mb
Defold with AppManifest Android apk 32 bit - 1.3 Mb
Unity Android apk 64 bit - 6.1 Mb
Defold Android apk 64 bit - 1.6 Mb
Defold with AppManifest Android apk 64 bit - 1.4 Mb
HTML5 (wasm only)
Unity
Folder: 2.8 Mb
GZIP: 2.7 Mb
Defold
Folder: 2.3 Mb
GZIP: 881 Kb
Defold with AppManifest
Folder: 1.9 Mb
GZIP: 734 Kb
iOS
Unity universal build ipa - 9.8 Mb
Defold universal build ipa - 2.6Mb
Unity universal build app - 30 Mb
Defold universal build app - 4.9 Mb
Projects
Defold Project: TestProject.zip (2.9 KB)Unity project:
TestProject.zip (21.3 KB)
Raw data
% tree --du -h
.
├── [ 17M] DEFOLD
│ ├── [1.6M] 32.apk
│ ├── [3.3M] 32_64.aab
│ ├── [1.6M] 64.apk
│ ├── [2.3M] HTML5
│ ├── [881K] HTML5.tar.gz
│ ├── [4.9M] universal.app
│ └── [2.6M] universal.ipa
├── [ 71M] UNITY
│ ├── [5.7M] 32.apk
│ ├── [ 11M] 32_64.aab
│ ├── [6.1M] 64.apk
│ ├── [2.8M] HTML5
│ ├── [2.7M] HTML5.tar.gz
│ ├── [ 30M] universal.app
│ └── [9.8M] universal.ipa
└── [ 13M] Defold-with-appmanifest
├── [1.3M] 32.apk
├── [2.7M] 32_64.aab
├── [1.4M] 64.apk
├── [1.9M] HTML5
├── [734K] HTML5.tar.gz
├── [4.3M] unitversal.app
└── [2.2M] universal.ipa
UPD:
I added measurements for Defold with the following AppManifest:
