One Apple Change And Kaboom!

The world is still going absolutely crazy over this:

3.3.1 — 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).

This guy has the most plausible explanation: Jobs makes a valid point: intermediate layers hinder the progress of the platform.

However, this one — Bravo, Apple — must be acknowledged for its sarcastic irony:

… all developers who wish to submit apps hold at least a 4 year degree in computer science. Just imagine a world where any kid can work out of his garage and build an application with an original language, or bit of hardware, that snubs its nose at the establishment – anarchy would ensue.

As a non-developer, it took me days to finally get to the point where I found an explanation that made some sense. There were those who offered tweeted explanations, but none of them were convincing because they came from people who generally don’t see Apple doing anything wrong (even when Apple does!).

How could a PR disaster like this happen? Apple has to know that developers are very noisy people when they feel they are being wronged. Clearly an explanation was needed, but no official statement was ever made. Although Steve Jobs replied to emails, why was it even necessary for him to address this issue personally? That’s what PR people — if not simply Developer Relations — handle.

Why do I bother to keep it alive on this blog too?

Because, at some point, Apple is going to change the TOS for iPhone, iPod Touch, and iPad users. This is inevitable in order to accommodate the data collection required to properly serve up iAds.

So Apple had better have a plausible, clear, and sympathetic story all ready for when that day comes.

5 responses to “One Apple Change And Kaboom!

  1. Hmmm…
    1) Do consumers (customers) even hear about this stuff?
    2) When has a user ever read the terms of service? If changed, back to #1

  2. “How could a PR disaster like this happen? Apple has to know that developers are very noisy people when they feel they are being wronged.”

    I think the bigger question is why is Adobe acting shocked and surprised. I can’t believe that they didn’t see this coming. They’re playing this up to fan the flames of public opinion to try and embarrass Apple into supporting flash.

  3. Google Wave. Nuff said.

  4. I understand this position, but the shockwave it can start with iPad development can be tooooooo big. imagine Time and other magazines having to code their Apps form the scratch instead of using something like Woodwing plugin for InDesign….

    I believe it can be a good position for closed applications, but for magazines? It can be a dangerous road…

  5. Whoa. I hadn’t even considered the magazine angle!