I actually knew about this while writing the other post, but it hadn’t seemed to break publicly on the Net yet. Well, now it has. There’s language in the new SDK agreement for iPhone OS 4.0 that appears to ban using any development environment or toolchain that Apple doesn’t like. Most especially, it seems aimed at preventing Adobe from marketing the flagship feature in CS5: compiling for iPhone standalone apps.

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

CS5 launches on Monday, by the way, so this is a huge blow to Adobe.

There is already plenty of speculation as to whether this catches stuff like Unity, MonoTouch, Appcelerator (they had a blog post up about it, but it’s gone now!), and who knows what else. Basically, all cross-compilation tools, which is a large amount of the middleware out there.

This is the dark side of the last post I wrote. Epically closed means, well, epically closed. And in this case, it means creating barriers to content creation that effectively mean it costs more dollars to engage in the market. That’s what happens when you have closed-off production-and-distribution chains: smaller developers lose out.