iPhone OS 4, Flash, Adobe, and the game to play

Referencing this MacRumors.com post: Adobe Acknowledges That Apple’s Flash Prohibition Could Harm Business

Adobe says this:

Additionally, to the extent new releases of operating systems or other third-party products, platforms or devices, such as the Apple iPhone or iPad, make it more difficult for our products to perform, and our customers are persuaded to use alternative technologies, our business could be harmed.

One day following Apple added this to their iPhone SDK rules:

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

(see Daring Fireball’s summary 1 and summary 2 for more info.)

This is all about Adobe adding a “Save as iPhone App” export option to Flash CS5.

I suggest to Adobe: Strengthen your other products which would be beneficial for iPhone use.  Dreamweaver is an extremely popular web creation tool.  How about some iPhone/iPad-optimized web templates?  Perhaps support for HTML5′s offline storage?  Maybe package and save a site out as fully offline-capable web app savable to a user’s home screen?  Yes, you can do that – write standard HTML5/Javascript and fully bypass the App Store with what looks to most people as a native app.

Similarly, Premiere could be strengthened with better Quicktime support such as HTTP Live Streaming – something Apple doesn’t even support yet with Final Cut Pro.

Adobe has lost its battle to put Flash on the iPhone.  Dead, gone, kaput.  This is a good thing.  Adobe should forget about the game it can’t win, and focus on the game it can.