Wednesday 27 August 2008, 11:32 AM
Apple tried open source defence in ad case
The adjudication actually makes pretty interesting reading. For a start, Apple was trying to argue that the iPhone is better than cheap featurephones for web browsing (true, but not the point), but here's the really brazen bit:
Apple said the Safari web browser on the iPhone was built to open internet standards, the same as Safari on a home or office computer, and supported open standard languages such as CSS, JavaScript and Ajax. They said proprietary languages or technologies, such as Flash or Java, were not open source and required a plug-in or individual download in order for content to appear within the specific browser, regardless of whether the access to a site was made from an iPhone or home computer. They said they could not ensure compatibility with every third party technology in the marketplace and, in order to create the best customer experience, had created their platform on open standards. They said Java and Flash were examples of proprietary software they had chosen not to enable on the iPhone.
Say what? So, to translate: "We at Apple only want to use open standards. We won't include stuff we can't control. It's for the user's own good. Even if they can't access all the intarwebs as promised. Unless they're using Safari on the desktop, in which case this argument doesn't apply." Is that about right? If so, it's certainly a thought-provoking approach to take...
Comments on this post
Classic Apple, but David what is the reason that java or flash is not built into the iPhone browser is it so very hard to do ?
Utz
Well, it would involve the iPhone users getting the plug-ins from Adobe and Sun, and Apple seems quite keen to keep itself the sole point of contact.
I think there is a grain of truth in Apple's argument - I mean, how annoying are Java updates on the desktop? But still, the argument as a whole just does not ring true, because it doesn't apply to desktop Safari at all.
It's worse that that! Javascript support on iPhone is some 80 times slower than a typical desktop or laptop computer, which means that it's also less capable at processing Web 2.0 sites. Struggling with Javascript typically means faster battery drain.


