A lot of what goes on in SWF files is the art data (vector graphics, the 'movieclip' object, etc). Flash comes with a pretty extensive API for manipulating gra

A lot of what goes on in SWF files is the art data (vector graphics, the 'movieclip' object, etc). Flash comes with a pretty extensive API for manipulating graphics and these objects, all which needs to be rewritten for mobile. There's a lot there, believe me. Unfortunately, much of that content is what causes the problem. Using the artist tools (Flash CS3), you can generate content that simply fumes memory, without writing a single line of code. I'm not sure you can even fix those issues without re-authoring the art content. What makes this worse is that anyone can embed one of these crappy SWFs in a webpage, causing the browser to fume memory too.