That is not good news. Can you talk a little bit about what components you used if any and if your code is mxml heavy or you used more as3 classes? Not to try and back up adobe or throw dirt at you but it could very well be the way you developed the app and what includes were compiled with the application that make it big and slow.
Certainly. I would be glad to share the specifics. I have the following classes:
StationLocator (MXML class): 1,627 bytes
StationLocatorHome (MXML class): 2,597 bytes
MapView (MXML class): 4,789 bytes
Location (AS3 class): 4,132 bytes
GeographyEvent (AS3 class): 349 bytes
GeographyWSAO (AS3 class): 5,641 bytes
3rd Party Components
map_flex_1_20.swc 90,278 bytes
Of course, when you generate a new Mobile App project, it creates the StationLocator and StationLocatorHome MXML classes, based on your project name. So, I have those two MXML classes, plus a MapView class for Google maps. The rest are AS3 classes, along with the Google mapping component.
I've tried deploying it both with the Framework linkage set to "Merged into code" and "Runtime shared library(RSL)". Both perform basically the same. Lousy!
I'm going to re-do this project in Eclipse Java environment with the Android plug-in and SDK, and see how that performs.
Are you looking at the size of the release APK or the debug APK?
(For release APK, go to Project -> Export Release Build.)
That's the release apk. The debug apk was 1.5 meg
I'm not sure why, but this application is now seeming to perform well. So, I'm going to chalk this up to "unknown" at this time. I can't really say whether the previous slowness was due to Adobe Burrito, something in my design that has gotten resolved, slowness of Google maps, or what. But, right now, I"m happy with its response.
See my last post for "solution".
Maybe other apps on your device were slowing it down? Just throwing that out there.
I'm new to Burrito and FB development and i detected the same issue during my work. I completed this tutorial here:
and when i test it on my Google Nexus S, the List seems to be very slow and
compared to lists done in eclipse with the android SDK it's just awful.
Is this because of the testing environment? Perhaps the compiled apk file will
work better. i didn't try it..