Burrito Mobile Apps Extremely Slow

Question

I just deployed a simple little app, built with Adobe Burrito. it has a list view for locations and a map view for Google maps. You touch a location in the list and it displays your location (obtained via GPS) and the selected location. Simple. Yet, it deploys as a 650K app and runs like tortoise in quicksand. And, I'm on a HTC Evo, which has a snapdragon processor.
First, seems like the deployed apk is way to big, and second, it's an embarrasment in terms of performance when compared with other apps. The painting of the map is like watching a 300 baud modem display an old telnet session.
I hope Adobe plans to make big improvements or this is going nowhere in the arena of mobile app development.
Ron Grimes

Answer 1

Certainly. I would be glad to share the specifics. I have the following classes:
     StationLocator (MXML class):         1,627 bytes
     Views
     StationLocatorHome (MXML class):     2,597 bytes
     MapView (MXML class):                4,789 bytes
     Supporting Classes
     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.
Ron