Apple Bans Adobe Flash Compiler for iPhone--Does Limiting the Development Platform Stifle Innovation??
My "Patty's Pioneers" group has been actively (and privately) debating the reasons behind, and the ramifications of Apple's recent changes to the Terms Of Service (clause 3.3.1) in the iPhone software development agreement described in this post by John Gruber: New iPhone Developer Agreement Bans the Use of Adobe’s Flash-to-iPhone Compiler.
We've had interesting technical debates about whether there are good technical reasons why Apple should not support Adobe's development tools and compilers--too slow, too buggy, too insecure? Make it easier to migrate to a next generation chip?
We've also debated the pros and cons of using cross-platform development tools for mobile applications--write once, run anywhere--or writing platform-specific applications using platform-specific tools.
We've debated whether Apple is looking out for the customer to avoid a lousy customer experience, or looking out for Apple--to ensure a more profitable revenue stream by controlling the flow of money thru iTunes.
We've bemoaned the investment that companies with sophisticated Flash applications will have to make in order to re-develop them for the iPhone, if this war continues.
But what I think has captured all of our imaginations the most is the quite public feud going on between Apple and Adobe.