Adobe claims Apple 'collaboration' on iPhone Flash
We're working on it (again)
Adobe CEO Shantanu Narayen has spun yet another pirouette in his company's dance with Apple regarding the development of a Flash player for the iPhone.
"It’s a hard technical challenge," Narayen told Bloomberg last week at the World Economic Forum in Davos, Switzerland, "and that’s part of the reason Apple and Adobe are collaborating."
The "challenge" part isn't news, seeing as how Flash was developed for the desktop and not for the low-powered CPU and small memory footprint of a handheld device such as the iPhone.
But has this been the only reason for the delay of Flash on the 'Phone? After all, last June, Narayen told analysts who asked about progress on the project: "We are working on it. We have a version that’s working on the emulation." He went on to say that Adobe was "pleased with the internal progress that we’ve made to date."
Which, as we all know, didn't happen.
Which leads us to the second half of Narayen's statement, that "Apple and Adobe are collaborating."
Apple strictly controls what it allows to grace the slender confines of its darling phone. And Apple's EULA for the iPhone SDK includes the following directive: "An Application may not itself install or launch other executable code by any means, including without limitation through the use of a plug-in architecture, calling other frameworks, other APIs or otherwise...No interpreted code may be downloaded and used in an Application except for code that is interpreted and run by Apple's Published APIs and built-in interpreter(s)."
At least officially, apps that run other code - such as Flash and Java - need not apply.
Plus, Apple has publicly badmouthed Flash. At a shareholders' meeting last March, just before the iPhone SDK arrived, Steve Jobs said that Flash Lite, a downsized version of Flash designed for mobile use, was "not capable of being used with the web" and "performs too slow to be useful."
But it's been nearly a year since that statement, and a lot of improvements can be made in that time - especially if, as Narayen says, "Apple and Adobe are collaborating."
And the EULA limitations are Apple's to wield as it wishes. If you make a rule, you can break a rule - after all, an offended Sun Microsystems is no skin off Apple's corporate schnoz.
Narayen's statement could be a signal that the long-awaited Flash player has been quietly green-lighted by Apple.
Or the Adobe CEO could be simply blowing smoke, hoping to buy some more time as he continues to plead with Apple for a spot on the iPhone.
"The ball is in our court," he said. "The onus is on us to deliver."
And the onus is on Apple to approve that delivery. ®
too hard to do on a mobile device?
What exactly is hard about writing a flash player for the iphone? I've had a perfectly good flash player on my N95 for over 2 years now, with no issues... I don't see any difficulty here in making it work on a mobile platform, power consumption or memory usage wise...?
The solution to this...
is for it to work just like the current QuickTime media player does on the iPhone. Only playback what is actively loa tded by the user in a standalone app, rather than have it load on the webpage. That way, it is the user who gets to dictate how much battery life they want to be sucked up by Flash.
Re: I think I know what's going on
"It's starting to sound like the programmer who wrote Flash for Adobe quit the company and they're scrambling to recover."
Given that Adobe got Flash via the acquisition of Macromedia, there's a very good chance that that particular horse bolted a long, *long* time ago.