{"id":2897,"date":"2010-04-21T14:38:23","date_gmt":"2010-04-21T22:38:23","guid":{"rendered":"http:\/\/www.perivision.net\/wordpress\/?p=2897"},"modified":"2010-04-21T14:38:55","modified_gmt":"2010-04-21T22:38:55","slug":"no-flash-for-iphone-ipad-or-i-anything-really","status":"publish","type":"post","link":"https:\/\/www.perivision.net\/wordpress\/2010\/04\/no-flash-for-iphone-ipad-or-i-anything-really\/","title":{"rendered":"No Flash for iphone, ipad or i anything really."},"content":{"rendered":"

Well, Adobe gave up the ghost and has announced that it will no longer continue to invest in building a tool that will allow Actionscript programmers to write for the iphone.\u00a0 Although the shock of Apples c*(k -blocking has already warn off, its still a bit depressing.<\/p>\n

\"\"<\/a>

image from iphonebuzz.com<\/p><\/div>\n

There has been many arguments that Apple needed to do this to protect to the product, all of which are basically rubbish since the resulting code is compliant to the API, its really a business decision. And as I said, I can see the merit in the decision. By keeping control over the developers to do things the Apple way not only provides more control but provides more profit by forcing some dev’s to make a choice to between learning coco or some other mobile SKD language.\u00a0 It also forces smaller dev house to choose which platform to develop for, and right now, the iPhone is king.\u00a0 So if you are a small shop and can only afford to dev to one target, you are going to build for Apple and thus will NOT build for Android or Windows or whatever.<\/p>\n

Now the is a possibility this could backfire.\u00a0 If Android gets a larger marker share then Apple, then dev house will create for Android first, Apple second.\u00a0 But that day seem quite far off.<\/p>\n

Rest in peace iPhone Flash; we hardly knew ye.<\/p>\n

Related Posts<\/H3>