I don't really buy the premise that Flash can't be implemented on iPad merely because of some user interface details. Most smartphones will be going to some form of touch interface in the next year, if they haven't already. Adobe wouldn't have announced their latest Flash Player 10.1 and Adobe AIR at Mobile World Congress if the touch interface couldn't be used in some way. See
Adobe Announcements at Mobile World Congress 2010 (Adobe Featured Blogs) for copies of the announcements.
The Flash developer even proposed the logical solution to the problem: Touch replaces mouse-over, and tap or double-tap replaces mouse click selection. Then after proposing it, he dismisses as unworkable because he somehow thinks its too complicated. Oh, please. . .
The problem really is Flash performance on the Mac, and by extension, to the iPhone OS, which, as Tim Cook pointed out, is merely a version of Mac OS. As a dues paying member of the iPhone Developer Program, I can attest to this often misunderstood fact. So poor Flash performance in Mac OS translates into even worse performance in iPhone OS, given the very limited processor resources available in the Samsung chip.
It is certainly open to question, who's to blame, Adobe or Mac OS for the poor performance. I prefer not to speculate on this. The solution is still the same either way: Apple and Adobe need to collaborate on an efficient version of Flash for Mac OS.
For more on this see my blog at
Mark's Tech Chat
Mark Hibben