Smaller executable footprint?

[Jim Brown]

I am *very* pleased with the final size of the Basic4Android executions (typically 200k using core library features)

One thought though, could the final executable be squeezed further through obfuscation?
Not that it matters a great deal to me. Here is a size comparison of an app I have written in three languages:

Android SDK (Java) == 18Kb
Basic4Android == 220k
AppInventor == 1.92MB (!)


Development wise, the Android SDk version took me around 4 days to get working. I was forever fighting with Java's various errors.
AppInventor is really nice, offering a Lego-Type plug and go design method. Although things are limited at the moment. The file size is large too.
As for Basic4Android, I knocked up the equivalent app in 2 hours. It works like a charm. Hats off then for the design and implementation of Basic4Android !

 

[Erel]

One thought though, could the final executable be squeezed further through obfuscation?

I haven't tried it myself but I don't think that it will improve a lot.

Note that this size is mostly related to the core library. Which means that it will not grow too much when your program grows.
And also note that most other libraries are pretty small. Users are encouraged to use libraries as needed and not try to save several kilobytes.