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

That’s pretty much a declaration of war against Adobe. They’re just days away from releasing an amazing Flash CS5 release featuring… *drumroll*… a packager for iPhone OS, targeted at iPhone, iPad, and iPad.

“Applications must be originally written in Objective-C, C, C++, or JavaScript” – who do they think they are? They want to tell the developer which tools to use? Apple’s trying to change the nature of the Web, and they’re swinging their weight to have things run their way.

It’s basically the same way how Microsoft achieved their current position, as John Gruber put it:

At a certain point developers wrote apps for Windows because so many users were on Windows and users bought Windows PCs because all the software was being written for Windows. That’s the sort of situation that creates a license to print money.

I still think the way Adobe managed to circumvent the obstacles for Flash Platform content on iPhone OS was brilliant. I’ve seen it as a way to show Apple the proverbial finger.

Yes, Adobe is a multi-billion company, too, but over the last few years, Adobe has consistently tried to alleviate development for the Flash Platform, opening up where they see fit (Flex SDK, BlazeDS, OSMF, TLF etc.). Of course there are some questionable products (e.g. LCDS).

Apple’s efforts to protect their cash cow AppStore makes Microsoft look pale in comparison. Apple’s about the create the most closed ecosystem you can think of. Of course, they have strong allies: with many of the major players like Google shifting more and more towards offering services for free, content providers may see the AppStore/iBookStore/iTunes ecosystem as some sort of last chance to cash in on their content.

I really believe in the free and democratic nature of the internet. Since the birth of the AppStore, Apple has shown some blatantly brazen attitude in deciding which apps to feature in the AppStore and which not. Until now, they got away with it because the developers wanted to go with the masses.

But now, the tone has changed. Apple has made it clear that they’ll try to squeeze every single possible penny out of their closed ecosystem before even thinking about enabling open innovation. Allow other forces to exert control over content on the iPhone/iPod/iPad? No way. Pay the 30% Apple tax and shut up. Want to develop for those devices? Pay $99 before you even think about it.

Just 18 months ago I switched from PC to Mac, partly because I still didn’t like the way Microsoft had played the game to make Windows the dominant OS on desktop computers. Now the way Apple tries to strong-arm their way into the mobile market makes me retch.

I can’t help but think of the Dark Force and see that Applekin has turned to the Dark Side.

Obi Wan Adobe, I’m with you. Microsoft, you’ve improved a great deal over the last few years, pushing innovation. Maybe we could become friends after all.

After Adobe got much heat about performance and stability issues in the Creative Suite 4, there’s a good chance that the new set of creative products will meet the high expectations in the creative community. Public betas and previews at last year’s Adobe MAX 2009 conference in Los Angeles, California, hinted at an impressive amount of new features. Flash Platform developers, for example, will welcome the possibility to target the iPhone from Flash CS5.