I just found out something rather surprising.
I have this lavish application in Classic Thunkable; it is making use of nearly all the features and components, some of which are still not available in X (canvas for instance), has 5 screens, over 7000 (not a typo, I do mean over seven thousand) blocks, has 13 media files, hundreds of components, etc etc. The resulting .apk file is 4.57 MB. Once installed, the app occupies 25.09 MB in internal storage in one of my device (another reports 16.32 MB, go figure why it is less…)
On the other hand, there is a user who just posted a question “why is my app failing?”, which is a VERY simple app (2 screens, 163 blocks, 25 components; nothing fancy, it is just a test app), but the .apk is 19.6 MB and once installed, it takes 77.99 MB of internal storage !
My question is “why”?
Is that something that has been observed or reported before?
Why is an X app that does virtually nothing ends up taking 3+ times the memory of something that does everything, including helping you computing the volume of your kitchen sink, based on Classic?
Can anyone else validate that the same functional app is taking so much more memory, having much larger .apk files when written in X than in Classic?
Can anyone also validate that the iOS files in X (for the same app) are comparable in size to the corresponding .apk for the Android side (I do not have an iOS device, so cannot validate that, as far as I can tell)?