Quote:
Originally Posted by
Suddenly Newton 
Maybe. Apple doesn't allow runtime interpreters and virtual machines on iOS, if I recall correctly. This would mean any Flash "translators" would have to emit Objective-C source or LLVM instructions to get around the restriction. A quick web search netted the answer: LLVM.
http://www.adobe.com/devnet/logged_i...od_iphone.html
Adobe simply created an ActionScript front-end to LLVM. Optimizations are done to LLVM code before compiling it down to native ARM assembly.
That would explain some things...
1) AIR appears to run acceptably fast and [mostly] responsive on an iPad 2
2) but AIR apps don't act quite right:
-- no variable-speed scrolling - flick, fast start, then slow down
-- no bump/bounce when the end of a scroll is reached
-- scroll always centers on an item
-- no universal pinch-zoom capability within the app
-- apparently no capability to handle more than 2 concurrent touches
-- noticible lag when dragging - the hand moves, then the dragged item moves
3) I suspect that using Flash-generated general functions is less efficient than native iOS specific functions
4) Not sure if AIR is robust enough to exploit iDevice features across several iOS versions
I get the impression that AIR iOS apps are lobotomized to make them "just acceptable" for iDevices, so that the same code base can be used for Android, QNX...
It's almost like the Adobe-generated "magazine" apps -- they're all content...
They don't appear to use any standard UI, expected iOS features don't work, and the UX is confusing and unsettling...
They're just there...