Apple’s Jobs Defends Flash Claims

JobsMacManagementMobilityProjectsSoftwareTabletsWorkspace

Apple CEO Steve Jobs has given a series of reasons why Apple does not support Adobe’s Flash on its mobile platforms

In what amounts to a pot meets kettle moment, Apple CEO Steve Jobs has laid out a series of reasons why Apple does not support Adobe’s Flash on its mobile platforms.

Flash not fit for Apple products

In essence, Jobs said Flash is not fit for Apple’s iPhone, iPad and iPod platforms, claiming that, among other things, Flash is not secure, reliable or touch-compatible enough and doesn’t perform well enough to run on Apple’s hot mobile consumer products.

But perhaps the boldest statement in Jobs’ 29 April post was that he believes Adobe Systems is closed and Apple is open. If that is not the pot calling the kettle black … Said Jobs: “Adobe claims that we are a closed system, and that Flash is open, but in fact the opposite is true.”

Jobs further explained, “Adobe’s Flash products are 100 percent proprietary.” Indeed, they are. He acknowledged that “Apple has many proprietary products too.” Then, setting the tone for his entire argument, Jobs added:

“Though the operating system for the iPhone, iPod and iPad is proprietary, we strongly believe that all standards pertaining to the web should be open. Rather than use Flash, Apple has adopted HTML5, CSS and JavaScript—all open standards. Apple’s mobile devices all ship with high performance, low power implementations of these open standards. HTML5, the new web standard that has been adopted by Apple, Google and many others, lets web developers create advanced graphics, typography, animations and transitions without relying on third party browser plug-ins (like Flash). HTML5 is completely open and controlled by a standards committee, of which Apple is a member.”

First off, neither has an “open” leg to stand on here. Both companies are closed, and as Bobby Brown said, that’s their prerogative.

Jobs listed all the ways that Apple supports open standards with HTML5 and so on, and delivering the WebKit engine. And Adobe argues that Flash is not 100 percent proprietary because the Flash file format is available here.

Apple wants control

But the bottom line is this whole argument is about control. Apple wants and deserves control of its platform, and clause 3.3.1 of its iPhone 4.0 developer license agreement spells that out. That clause reads:

“Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited).”

Moreover, Jobs said: “Adobe has characterised our decision as being primarily business-driven—they say we want to protect our App Store—but in reality it is based on technology issues.”

Well, it is and it isn’t. Indeed, there is merit to each of Jobs’ technological claims about Flash. Practically every user has at some point had some kind of negative experience—such as a crash or other glitch—due to Flash or applications and websites built with Flash. But this is still about control. Jobs can talk all he wants about video support, security, battery life and the like, but the key is Apple’s control over the development process. Apple cannot and will not afford to let Adobe and Flash get in the middle of Apple’s pipeline to its developers. And as his last, most cogent point, Jobs said exactly that:

“We know from painful experience that letting a third party layer of software come between the platform and the developer ultimately results in sub-standard apps and hinders the enhancement and progress of the platform. If developers grow dependent on third party development libraries and tools, they can only take advantage of platform enhancements if and when the third party chooses to adopt the new features. We cannot be at the mercy of a third party deciding if and when they will make our enhancements available to our developers.”

Read also :

Click to read the authors bio  Click to hide the authors bio