With the apparent iPhone 4.0 SDK ban on cross-compiled code, Adobe has begun firing back at Apple. The New York Times Bits Blog carried the following statement from Adobe:

We are aware of Apple’s new SDK language and are looking into it. We continue to develop our Packager for iPhone OS technology, which we plan to debut in Flash CS5

The TheFlashBlog (which readers might remember from iPad porn posts past) took it far more personally:

What is clear is that Apple has timed this purposely to hurt sales of CS5. This has nothing to do whatsoever with bringing the Flash player to Apple’s devices. That is a separate discussion entirely. What they are saying is that they won’t allow applications onto their marketplace solely because of what language was originally used to create them. This is a frightening move that has no rational defense other than wanting tyrannical control over developers and more importantly, wanting to use developers as pawns in their crusade against Adobe. This does not just affect Adobe but also other technologies like Unity3D.

[...] Now let me put aside my role as an official representative of Adobe for a moment as I would look to make it clear what is going through my mind at the moment. Go screw yourself Apple.

The timing does seem interesting. Apple could have put this in iPhone 3.2 for iPad. They could have skipped iPhone 4.0 betas and put it in the final iPhone 4.0 GM release (rendering wasted all the apps (time and money) developers had built using CS5 between Flash release and iPhone 4.0 release).

The timing could be to hurt Adobe CS5 sales (though certainly lots of creative professionals use CS5 for reasons that have nothing to do with Flash cross-compiling) or it could be an advance warning to developers not to use those tools because they won’t be allowed (or perhaps even compatible) with the final iPhone 4.0 release. Spending several months making an iPhone app in CS5 and then not being able to run it under iPhone 4.0 would be worse.

Ultimately, the language used by Apple is unclear and everyone is going to waste a lot of time and worry until it’s clarified.

Adobe fires back at Apple over cross-compiler ban is a story by TiPb. This feed is sponsored by The iPhone Blog Store.

TiPb - The #1 iPhone, iPad, and iPod touch Blog

Daring Fireball discovered that, as part of Apple’s newly released iPhone 4.0 beta, the licensing agreement now seems to ban binaries compiled by Adobe’s upcoming CS5, Mono Touch, and the like:

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 seems to mean that cross-compilers, which let you develop in the soon-to-be-announced Adobe Flash CS5, the C# and .NET-based Mono Touch, or similar environments and spit out iPhone-compatible binaries at the end, are being prohibited.

Unity, which is used by many large iPhone game developers, creates Xcode Cocoa touch projects (the native iPhone frameworks) rather than binaries so it may not be effected. Given the importance of iPhone gaming and the companies developing them, it’s hard to see Apple going hard-line against them the way they’re stamping so very firmly on the neck of Adobe, Mono, etc. here.

As to the reasoning behind this change, Daring Fireball posits:

And, obviously, such a meta-platform [Flash or Mono sitting on top of Cocoa] would be out of Apple’s control. Consider a world where some other company’s cross-platform toolkit proved wildly popular. Then Apple releases major new features to iPhone OS, and that other company’s toolkit is slow to adopt them. At that point, it’s the other company that controls when third-party apps can make use of these features.

In other words, it once again highlights Apple’s device-centric philosophy. They want beautiful boxes that run commodity apps and services. Adobe, Mono (even Google) want commodity boxes that run their apps and services. Those diametrically opposed points create these conflicts.

Pragmatically, selfishly, and completely from a user’s perspective however, I’ll take great, dedicated developers making apps specifically and purposefully for the platform (in this case, iPhone) any day over the code-once-spit-out-everywhere approach that has never delivered on that promise (other than with ugly, janky Air and Java apps).

Adobe CS5 with iPhone compilation launches in less than a week.

Apple updates iPhone 4.0 SDK agreement to block Flash CS5, Mono touch, cross-compilers is a story by TiPb. This feed is sponsored by The iPhone Blog Store.

TiPb - The #1 iPhone, iPad, and iPod touch Blog

iPhone, iPad, and iPod Touch developers: get yourself over to Apple’s developer center, as iPhone SDK 3.2 Beta 4 is ready for you to download, a mere two weeks after Beta three was unleashed for your coding pleasure. As MacRumors and Engadget note, it’s too early to say what magical new capabilities are to be found here – but don’t let that stop you.

iPhone SDK 3.2 Beta 4 is Out is a story by TiPb. This feed is sponsored by The iPhone Blog Store.

TiPb - The #1 iPhone, iPad, and iPod touch Blog

The Electronic Freedom Foundation (EFF) petitioned NASA (an iPhone developer – iTunes link) under the Freedom of Information Act to provide them with a copy of Apple’s iPhone SDK License Agreement, and have gone through and provided both a link to the agreement (an older version, provided at the time of the request) and some analysis of what it contains.

For those not familiar with the document, it contains the legal terms a developer must agree to before they can develop for the iPhone platform. Since the EFF and Apple have been duking it out over Jailbreaking for a while now — the EFF wants Jailbreaking to be made an official exception to the Digital Millennium Copyright Act (DMCA) and Apple has opposed that move — the EFF thinks the SDK agreement is particularly interesting at the moment.

The major points brought out and up by the EFF include:

• One rule of the SDK license agreement is you can’t talk about the SDK license agreement. Despite it not being “Apple confidential information” developers are contractually prohibited from discussing it in public.
• Apps developed using the SDK can only be released through the iTunes App Store. So if Apple rejects you for any reason, according to their own guidelines or just on whim, you can’t release via Jailbreak or on a competing platform (if any were compatible).
• No reverse engineering or helping others reverse engineer, even where such actions have legal precedent as exceptions to copyright.
• No hacking or helping hack any Apple products. That means no Jailbreaking the iPhone, no putting Boxee on your AppleTV, no loading Linux on your iPod Classic.
• Kill switch is informed in the agreement. Apple can revoke your certificate at any time. (Though they’ve yet to ever do this).
• If Apple messes up and owes a developer damages, those damages will never exceed $50, so good luck suing for millions over your rejected Sexy App or RSS Template.

The EFF is none to pleased at the one-sided, gate-kept, stifling terms of the SDK Licensing agreement and good for them. And good for us as well. The way we look at it we need the opposing forces of Apple Legal and the EFF always pushing for more on both sides. Apple’s going to want to protect themselves as much as possible and the EFF is going to want to show us every way they’re doing it so if we don’t like it, we can voice our concerns as well.

We’ve used the analogy of restaurants before. The iPhone is Apple’s boutique, haut-cuisine eatery. They set the menu. You can’t go there, demand a burger, and then throw a fit when they tell you they don’t serve it. (Well you can, but you’d be nuts — Apple’s not in the business of serving burgers). Instead of Gordon Ramsey you get Steve Jobs crafting your dining experience, and if you go there, that’s what you should expect — to trade control for ease of use (as opposed to Google where you trade privacy for free service). However, the EFF making sure the ingredients are what we’re told they are, and that the kitchen is kept clean and compliant with local ordinances — that’s good for us, and ultimate it’s good for Apple.

Check out the EFF article, take a look at the agreement, and let us know what you think.

[Thanks to Fassy for the tip!]

EFF Uses NASA to Out iPhone SDK License Agreement is a story by TiPb. This feed is sponsored by The iPhone Blog Store.

TiPb - The #1 iPhone, iPad, and iPod touch Blog

UPDATE: We’re getting really scattered reports, but it looks like the site has a new look/feel, a new $99 developer option for Mac (to match the $99 iPhone option), and…? Let us know if you see anything else.

Also, some developers have told us that their registration no longer works after the update, so there may be some bugs at work. Let us know if you’re having any problems accessing iPhone 3.2 or other resources.

ORIGINAL: It’s not the Apple Store, but 9to5Mac is reporting that Apple’s iPhone SDK developer portal, developer.apple.com is down:

We are busy updating the site. Please check back soon.

We know it won’t be new MacBooks, so any guesses as to what it will be? We’ll update as soon as we know!!

UPDATED: developer.apple.com/iphone Down! is a story by TiPb. This feed is sponsored by The iPhone Blog Store.

TiPb - The #1 iPhone, iPad, and iPod touch Blog