OS 4.0’s Developer Agreement Slaps Adobe, Flash

This image described by iPhone, Apple, Adobe, Flash, OS 4.0, Adobe_flash_logo1

Steve Jobs has never made any secret of his dislike for Adobe Flash, and thus lack of Flash support on all iDevices to date shuts out users from gigabytes of Flash-heavy web sites (e.g. Hulu).  Meanwhile, Adobe thought it had figured out an end-run around Apple's "No Flashing Allowed" policy, as the upcoming Flash Professional CS5 could take native Flash projects and transmogrify them into iPhone-friendly (and, hopefully, App Store-friendly) applications.

Uncle Steve, unfortunately, had an ace up his sleeve.

In the wake of the OS 4.0 announcement, John Gruber of Daring Fireball was perusing the developer's agreement, and stumbled over the following clause relating to "APIs and Functionality:"

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

Translated into non-codemonkey dummy speak: cross-compilers (CS5 being a glaring example of such) or any compiling process that goes outside the Apple-approved work flow won't be tolerated, much less approved for App Store sale.

No one at Apple is overtly singling out Adobe here, but the message is clear: You play with OUR Tinkertoys, or you don't play at all.

[Via the New York Times]

About Dactyl Anapest

Google + Profile