Adobe AIR, by working on a VM, leaves the desired performance in relation to the device's native language (either JAVA or Obj-C). This is further compromised when using many objects on the display stage or a line of code "too long".
"I work with Flash and Adobe AIR and I know how much it bothers, even on Desktop."
Some tips I took to decrease these crashes:
- Avoid using "alpha = 0" and whenever possible use "visible = false". With alpha, although the object is not seen, it remains on the stage and being rendered. With the visible this does not occur;
- "Copy" objects and not "Duplicate". Whenever possible use / add the same object on the screen;
- Beware of using filters and effects in MovieClips and TextFields, such as shadows, beziel, etc ... This in conjunction with a tween requires a lot of processor;
- There is a hint that helps a lot: render objects on the stage as Bitmap: Properties - > Display - > Render - > Export as bitmap ;
Otherwise I recommend testing on other devices and verifying performance. Many of the applications I created were simple, but without these issues with "lag", I think these tips will help a lot.
Unfortunately, Adobe AIR applications face this problem, that "there is no cure, just treatment."