| |||||||||||||
Android App Bloat??Android App Bloat??Posted May 16, 2012 23:38 UTC (Wed) by ldo (subscriber, #40946)In reply to: "Last year's phone" by Richard_J_Neill Parent article: Tasting the Ice Cream Sandwich
Richard_J_Neill Even a basic "flashlight" app is hundreds of kB... I don’t understand how you come up with that figure. Here is an app of mine that does something reasonably interesting, and includes built-in help, in a package that is just 59kB in size. And the built APK for this sample app is just half of that. Dalvik is a very compact byte code—half the size of Sun JVM bytecode. And all the additional XML resources for your app are stored in a compressed binary form. So I don’t see where the bloat should come from...
(Log in to post comments)
Android App Bloat?? Posted May 17, 2012 16:57 UTC (Thu) by zlynx (subscriber, #2285) [Link]
Don't some of the package formats for Android preinstalled software include the byte-code AND the compiled code?
Android App Bloat?? Posted May 17, 2012 22:30 UTC (Thu) by ldo (subscriber, #40946) [Link] I don’t understand what you mean. The byte-code is the compiled code.
Android App Bloat?? Posted May 17, 2012 23:49 UTC (Thu) by zlynx (subscriber, #2285) [Link]
Android version 2.2 (I think) introduced an optional JIT compiler which compiles the byte-code into machine-code.
I thought that the ODEX (Optimized DEX) format can contain a cached copy of the JIT-compiled machine code. I also believe that the ODEX format is commonly used for all applications which are included in a ROM, because each ROM is hardware specific anyway.
Android App Bloat?? Posted May 18, 2012 1:09 UTC (Fri) by ldo (subscriber, #40946) [Link]
None of which is relevant to ordinary apps like you or I might write.
|
|||||||||||||