define('DISALLOW_FILE_EDIT', true);{"id":718,"date":"2011-11-10T17:45:13","date_gmt":"2011-11-10T22:45:13","guid":{"rendered":"http:\/\/www.unfocus.com\/?p=718"},"modified":"2011-11-11T18:07:37","modified_gmt":"2011-11-11T23:07:37","slug":"adobes-flashair-messaging-nightmare","status":"publish","type":"post","link":"http:\/\/www.unfocus.com\/2011\/11\/10\/adobes-flashair-messaging-nightmare\/","title":{"rendered":"Adobe’s Flash\/AIR Messaging Nightmare"},"content":{"rendered":"

Update:<\/strong> Mike Chambers posted an explanation and clarification on where Adobe is headed with Flash and AIR<\/a>. Update 2:<\/strong> TechCrunch picks up (part of) the narrative.<\/a><\/p>\n

I published an old post with my thoughts on the “Flash is Dead” thing that pops up routinely in media circles after anything happens to shake things up (like an Apple ban on Flash, or Adobe dropping a supported platform, etc.) yesterday. I optimistically highlighted in that piece the promise that AIR technology represents – it\u2019s even in the title “Flash and AIR, Nothing But Opportunity<\/a>“. I really believe the technology represents, and could fulfill all the promise those of us down in the weeds perceive. I also believe that Adobe\u2019s Flash Platform engineers and evangelists also see that promise, and would like to see it fulfilled.<\/p>\n

Yesterday Adobe unceremoniously dropped support for an entire class of platforms. No more Flash Player in mobile browsers. It\u2019s not a terrible technical decision – working in AIR and native app land offers a ton more flexibility. It even makes business sense. Browser makers are increasingly hostile to Flash – Apple has never let it in the door on iOS (and never will), and Microsoft announced plans to kill off plugins even on the desktop in Windows 8 Metro interface. Browsers have become hostile territory for Flash, so it makes sense to move emphasis in the two directions the industry is headed – app store apps with AIR (which no one knows about) and HTML5 for browsers. In an important way, this does mean Flash is dead – it\u2019s not going to be in the browser going forward. It really is out of Adobe\u2019s control.<\/p>\n

But there\u2019s a problem. The longer Adobe\u2019s bumbles the messaging, the harder it is to say for sure whether there is a lack of commitment to their platform (including AIR), or if it is truly just a PR problem. This kind of announcement had an easy to predict effect on Flash\u2019s brand, yet there was no attempt to get out in front of that narrative that would show they are committed to the larger “Flash Platform” of which AIR is an important part going forward. In the non-technical parts of the industry – the media, managers, and creative side of production teams – they all heard Adobe Flash is out of mobile – use HTML5. It\u2019s even worse in client land, where the term “HTML5 app” is used regularly along with “app store” – this news was so harmful to them, that clients with existing Flash content, which can be ported to the app space easily with AIR, are really freaking out. I can tell them about AIR all I want, but it\u2019s hard for me to counteract all the media buzz (repetition is reality – brain science).<\/p>\n

But what if they got the right message. This kind of move could represent a real intent on the part of Adobe\u2019s leadership to get out of the Flash Platform altogether, and maybe out of the platform space entirely, and focus instead only on tooling to produce for the platform commons that HTML5 represents. Look at the kinds of decisions they\u2019ve made recently. Adobe has essentially dropped internal support for their “Flash Platform” on every system platform they can, by either straight up dumping it (Linux, mobile flash, TV), or by farming out porting and support to partners like RIM.<\/p>\n

On the other hand, Adobe and Flash evangelists and engineers seem committed to the “Flash Platform” which in an un-articulated narrative (narrative – it\u2019s how we think – more brain science), really means AIR in app stores (mobile and desktop), but I\u2019m not sure I\u2019m getting the same message from the real decision makers at Adobe. I don\u2019t know if it\u2019s intent, or just plain old bad PR judgement, but it feels like I\u2019m standing on the greasy platform, and it\u2019s getting pretty tough to hold my balance. Some folks are already sliding off.<\/p>\n

I think they are in it for the long haul, and they’ve even built some of their own apps on the little known Flash based mobile app technology that is AIR. But guessing someone\u2019s intent is problematic – that only makes the PR problem clearer. I shouldn\u2019t have to guess.<\/p>\n

It boils down to this. I know technology, and I know the Flash Platform. I know it has merit and potential. But if people can\u2019t tell if the decision makers at Adobe are serious about supporting it into the future, it’s going to be a tough haul to convince anyone to build anything on that platform. I already know a few platforms, including HTML, learning a new one isn\u2019t scary, but I really prefer Flash and AIR because of it\u2019s potential and even it\u2019s legacy, which has value (despite the tar Steve Jobs dumped on it). If Adobe can\u2019t or won\u2019t make it clear that they are committed to AIR and the Flash Platform, I\u2019ll have to find an alternative – and the decision won\u2019t be mine. At this point, we need a clear unambiguous statement of intent from Adobe – are you committed to the Flash Platform and AIR, or not? A public roadmap wouldn\u2019t hurt either.<\/p>\n","protected":false},"excerpt":{"rendered":"

Update: Mike Chambers posted an explanation and clarification on where Adobe is headed with Flash and AIR. Update 2: TechCrunch picks up (part of) the narrative. I published an old post with my thoughts on the “Flash is Dead” thing that pops up routinely in media circles after anything happens to shake things up (like … Continue reading “Adobe’s Flash\/AIR Messaging Nightmare”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[12,5,211],"tags":[],"_links":{"self":[{"href":"http:\/\/www.unfocus.com\/wp-json\/wp\/v2\/posts\/718"}],"collection":[{"href":"http:\/\/www.unfocus.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.unfocus.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.unfocus.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/www.unfocus.com\/wp-json\/wp\/v2\/comments?post=718"}],"version-history":[{"count":7,"href":"http:\/\/www.unfocus.com\/wp-json\/wp\/v2\/posts\/718\/revisions"}],"predecessor-version":[{"id":724,"href":"http:\/\/www.unfocus.com\/wp-json\/wp\/v2\/posts\/718\/revisions\/724"}],"wp:attachment":[{"href":"http:\/\/www.unfocus.com\/wp-json\/wp\/v2\/media?parent=718"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.unfocus.com\/wp-json\/wp\/v2\/categories?post=718"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.unfocus.com\/wp-json\/wp\/v2\/tags?post=718"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}