The new UI wars: Why there's no Flash on iPhone 2.0
17 Jun 2008 - 11:19pm
7 years ago
Many reasons have been floated for why Flash isn't a good match for the
iPhone: it's slow, it hogs CPU cycles, it drains the battery, it crashes too
often, it's not optimized for Mac OS X and so on. As obvious as these
reasons may be, even if all those *technical* issues could be solved
tomorrow, there would still remain a huge divide between Adobe and Apple on
the iPhone: who controls the UI?
In this highly charged and competitive marketplace to establish the next UI
paradigm for mobile devices, Apple is not about to give Adobe or any other
company free reins to dilute its brand proposition by introducing
cross-platform, common-denominator UIs and interaction patterns to be
mingled with Apple's carefully orchestrated multi-touch approach. So what
does that leave Adobe with?