theFWA has a great set of quotes from leaders in the creative industry about what transitions like the one from Flash to other technologies really mean. Beyond the rhetoric, these are the tools of a community, and it is the creativity that is the real strength, not the platform. Also, a great Freudian slip in the use of the word “canvas” :
…”The relevancy of Flash and potential of HTML5 both lie in the hands of the creative community. More importantly, the future of the Internet remains a vast and exciting canvas so long as we seek to continually provide the most engaging and effective user experiences possible.”
–Jared Kroff, Creative Director, RED Interactive Agency
Adobe has made every effort to embrace the huge landscape of user interaction with data devices and because of their close connection to the developer community and open source aproach, they are able to bring some excellent solutions to all developers quickly. The turn-around time is really quite astounding. (although, like any good new feature, we all wanted it yesterday!)
One of highlights of the new FP11 is the use of the GPU accelerated 3D api for 2D rendering, focused specifically on 2D games. Lee Brimelow has a great starting tutorial here. I am a big fan of write-once, deploy anywhere, and that has always been a core concept of Flash Player. Adobe has embraced platforms beyond browsers and beyond the Flashplayer itself, and this flexibility and lack of ‘ego’ make them a solid partner for designers and developers. Some other great features in FP11 include native extensions, integrated runtime environment (basically no separate AIR download needed) and of course Stage3D (in cooperation with the best community-built 3D libraries!) and some good solid Flex UI components for mobile. So enjoy the new capabilities and the fact that Adobe does listen and cooperate and stay agile despite it’s strange position in a market with no direct competition but a constantly moving target.
That said, writing once and deploying as an app to multiple devices come with two prices – an incomplete API, and performance issues. The latter can be greatly affected by how code is written and what techniques are used or avoided, and any source of experimental results, like thie one below, are more than welcome. Still, Adobe has not only persevered but done an amazing job taking up the task of becoming not just browser independent, but mobile independent, leaving much of the quality risks and rewards to the programmers and designers: