Mike Adams

A lot has happened in the world of technology this week. Adobe announced their Creative Suite 5 on Monday. Apple announced their new MacBook Pro line on Tuesday. And in between it all, Apple revised their iPhone SDK (Software Development Kit) agreement, effectively killing what people have been clamoring for on their iPhone/iPod Touch. The agreement states the following:

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

What does this mean? Well…Adobe has been finalizing a work-around for being able to get Flash content onto your iPhone platform in the form of Flash CS5. In what is arguably one of the biggest features of the new Flash CS5 is that you would be able to do what you wanted to do in Flash, and then export it to several other platforms…including the iPhone platform. So what would be written in Flash could then be converted to the language needed to link to the API (Application Platform Interface). Which is really cool!

Now, Apple has seemingly stepped on this key feature for Flash. Sure, it could still compile for other platforms, but people have been begging for Flash on the iPhone OS since day one, and we thought we FINALLY had our work around. At this time, Adobe has no plans to change this feature and seems like they will see if Apple relents its grip on the “No Flash” policy they adopted.

Is it a coincidence though, that Apple released this revised agreement at the tail end of last week just before the big announcement of CS5? Was this done to take a little bit of the wind out of Adobe’s sails and get them into panic mode before the official announcement? And maybe, just maybe for that knockout punch, Apple also went ahead and announced their new MacBook Pro line today, almost assuring that the CS5 announcement of yesterday will be just that, a thing of the past. Again, I am not certain of any ill intent on Apple’s part, but it is a pretty big coincidence…