A little over a week ago Apple released a new draft of their iPhone developer program license which contained the following clause:
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).
Essentially, this has the effect of restricting applications built with a number of technologies, including Unity, Titanium, MonoTouch, and Flash CS5. While it appears that Apple may selectively enforce the terms, it is our belief that Apple will enforce those terms as they apply to content created with Flash CS5. Developers should be prepared for Apple to remove existing content and applications (100+ on the store today) created with Flash CS5 from the iTunes store.
We will still be shipping the ability to target the iPhone and iPad in Flash CS5. However, we are not currently planning any additional investments in that feature.
To be clear, during the entire development cycle of Flash CS5, the feature complied with Apple’s licensing terms. However, as developers for the iPhone have learned, if you want to develop for the iPhone you have to be prepared for Apple to reject or restrict your development at anytime, and for seemingly any reason. In just the past week Apple also changed its licensing terms to essentially prohibit ad networks other than its own on the iPhone, and it came to light that Apple had rejected an application from a Pulitzer Prize winning cartoonist on editorial grounds (which Apple later said was a “mistake”).
The primary goal of Flash has always been to enable cross browser, platform and device development. The cool web game that you build can easily be targeted and deployed to multiple platforms and devices. However, this is the exact opposite of what Apple wants. They want to tie developers down to their platform, and restrict their options to make it difficult for developers to target other platforms. There is plenty of commentary online about this, so I won’t belabor the point, but I have included some links below that cover it more depth:
So, was all of the work on the iPhone packager a waste of time and resources? No, I don’t believe so. We proved that:
- There is no technical reason that Flash can’t run on the iPhone
- Developers can create well performing and compelling content for the device with Flash
However, more importantly, the teams implemented features (such as hardware acceleration and Ahead of Time compilation) that we will now be able to leverage for other devices and platforms. We have gained knowledge and experience that are being directly applied to Flash Player 10.1 and Adobe AIR 2.0 for other mobile operating systems.
Fortunately, the iPhone isn’t the only game in town. Android based phones have been doing well behind the success of the Motorola Droid and Nexus One, and there are a number of Android based tablets slated to be released this year. We are working closely with Google to bring both Flash Player 10.1 and Adobe AIR 2.0 to these devices, and thus far, the results have been very promising.
Because this is Flash, it is rather trivial to port games created with Flash that target the iPhone to target other operating systems, such as Android. At FlashCamp San Francisco on Friday night, David Wadhwani (GM and VP of the Flash Platform) showed off a number of games running on Android that had been created with Flash, many of which had already been deployed as iPhone games. My personal favorites were Chroma Circuit and GridShock created by Josh Tynjala of Bowler Hat Games. Both games were originally developed as browser based games and were then updated to target the iPhone (Chroma Circuit was featured on the iTunes app store). Josh recently updated and optimized them to target Flash Player on Android, and the results have been impressive. There have already been a couple of of developers who have moved their Flash based content from the iPhone to Flash on Android (couple of examples below) and I expect that this is a trend we will be seeing more and more of.
Here are some links to developers who originally targeted the iPhone with their Flash content and are now deploying to Android:
Both Flash Player 10.1 and Adobe AIR 2.0 for Android are in pre-release testing. If you are interested in being notified when we expand the testing, you can sign up at:
Personally, I am going to shift all of my mobile focus from iPhone to Android based devices (I am particularly interested in the Android based tablets coming out this year) and not focus on the iPhone stuff as much anymore. This includes both Flash based, and Objective-C based iPhone development. While I actually enjoy working in Objective-C, I don’t have any current plans to update and / or maintain my existing native iPhone applications (including the AS3 Reference Guide, and Timetrocity). As I wrote previously, I think that the closed system that Apple is trying to create is bad for the industry, developers and ultimately consumers, and that is not something that I want to actively promote. Don’t worry though, I definitely plan to get both Pew Pew and Bacon Unicorn Adventure running on Android and am planning on open sourcing both.
We are at the beginning of a significant change in the industry, and I believe that ultimately open platforms will win out over the type of closed, locked down platform that Apple is trying to create. I am excited about Flash Player 10.1 and Adobe AIR 2.0 and all of the opportunities that they will make available to Flash developers across multiple platforms (desktop, Android, Palm, Windows Phone 7, RIM, etc…).
NOTE : Please keep comments constructive and on topic. Off topic comments will be moderated / deleted.
