Even without using the Android SDK I've seen a lot of people complain on 
here about having issues with the load time of maps in AIR (there's some 
solutions like preload it in an offscreen window, but with the limited 
resources, even of a nice tablet this probably isn't feasible/helpful, 
though you can google about it if you'd like to try).  If you're writing an 
app strictly to be run on Android I advise using the Android SDK (this is 
all google after all anyway) and leaving AIR out of the mix, if your plan is 
to make this work across all platforms I'd suggest going the HTML/Javascript 
maps route, if you have the time money and willingness to do so I'd suggest 
making a common service layer for dealing with requests and building 
multiple presentation layers (Android/iOS/AIR).

-- 
You received this message because you are subscribed to the Google Groups 
"Google Maps API For Flash" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-maps-api-for-flash?hl=en.

Reply via email to