Distilling market noise into market sense

VisionMobile is the leading research company in the app economy. Our Developer Economics research program tracks developer experiences across platforms, revenues, apps, tools, APIs, segments and regions, via the largest, most global developer surveys.

The Flash vs. HTML5 Endgame

[In the debate of Flash vs HTML5, has the death of Flash been over exaggerated? Guest author Guilhem Ensuque peeks through thick layers of hype and facts to predict what the future holds for the mobile web].

The Flash vs. HTML5 Endgame

The last year has seen a flurry of announcements and debate around the rise of HTML5 and the fall of Flash. Some have even gone as far as declaring a “war” between the two, and predicting the “death” of Flash as the outcome. However, as Mark Twain once famously said: “The rumor of my death is an exaggeration”. As we’ll see, the jury is still out as far as the fate of Flash and Adobe are concerned.

A brief (abridged) history of the web
“HTML5” is the new high-tech industry darling, and not just in the mobile space. It has become a catch-all phrase with little meaning when taken out of context. Before we dig into the debate, it’s worth looking at what is HTML5 and where has it come from.

“HTML5” when used as a shorthand, covers of family of web technologies currently being standardised by the W3C and at various implementation stages by browser vendors. The “5” comes from the version increment in the W3C spec number: currently most of the content you read on the web conforms to the HTML specification version 4.01.

To understand what has driven the creation of this new version of web standards, we need to look at the evolution of the web in past years.

historyofwebIn the 1990s the World-Wide-Web emerged from academia to become the ubiquitous medium to share digital documents over Internet Protocol networks. The HTML4 spec was matured in that era, and has been very much geared towards read-only, document-oriented description and hyper-linking. HTML4 mixes typographical tags with document structure description, within the bounds of static pages and has limited support for script-driven page logic and forms (does anyone remember CGI?). In that era of the web, support for multimedia content was notably absent from the web specification; leading to heterogeneous plug-ins striving to provide video delivery in web pages (remember Real Networks? or having to choose the speed of your modem?).

In the 2000s, the web evolved towards more interactivity with the advent of the “Web 2.0” (yet another buzzword) and user-generated content, especially videos uploaded and then streamed over faster ADSL connections. However, the HTML spec did not fundamentally change (apart from an attempt by the W3C to migrate to the stricter XHTML syntax which has seen mixed results in terms of adoption). To cope with HTML4‘s inefficiencies in allowing designers and developers to create interactive “experiences” (i.e. not just documents, but bi-directional “applications” living in your web browser) a number of innovations were introduced :

  • JavaScript, Dynamic HTML and XML HTTP requests (a.k.a. AJAX) as a way to have thick-client app functionality in the browser, enabling users to interact with the web in a read-write fashion (not just read-only)
  • clear separation of page structure in HTML (through heavy use of <div> tags) as well as typoraphy and style in CSS (through an arcane and verbose syntax), leading to more pleasant user experience and richer page contents
  • PHP-scripted and database-powered back-end logic bolted on top web server systems. This e.g. allowed template-driven content management systems like WordPress and Joomla to rise to prominence, fueling the blog revolution.

These innovations brought the ability to present vast amounts of data in pretty-looking dynamic web pages which mash-in RSS feeds, emails, blogs, Facebook updates, and tweets, and bringing web pages a step closer to applications.

In that era, Flash (or rather the Flash Player) rose to become a ubiquitous browser plug-in for animated graphics and video. At the same time, Flash evolved to provide an out-of-browser Rich Internet Application platform with the AIR runtime and the Flex framework, albeit at a much lower penetration level than the in-browser Flash Player.

We are now at the dawn of the 2010s, and the overhaul of the HTML4 spec is long overdue. HTML5 aims to bring back into the core spec of the web the “side” developments of the previous era and improve on them with a heavy focus on web applications. It also aims to lay the foundations enabling the delivery of web content through a new medium: mobile devices, and ultimately the “Internet of Things”. That history is yet to be written, but we can now ponder about its beginnings and the future.

So, What is HTML5 Really ?
In the context of this new era, the “HTML5” shorthand refers to a family of web standards and browser technologies that span a range of topics:

  • A modernized web markup language: the true-and-only HTMLv5 specification and matching evolution in web browser capabilities. The new syntax includes the <canvas> tag allowing bitmap manipulation through JavaScript drawing APIs, better support for vector graphics authored in SVG, the <video> tag allowing streamed media playback as simply as embedding images and the streamlining of tag usage.
  • A richer styling language: the Cascaded Style Sheets v3 specifications. CSS3 is now famous for its ability to create rounded corners, but more importantly includes so-called “transforms” allowing graphical effects like moves, rotations, gradients, etc. as well as 3D graphical objects manipulations. Much effort as been put by browser vendor to support hardware acceleration for CSS3 rendering. However, the standard is not yet mature and today requires using prefixes specific to each browser.
  • Application-oriented advancements in the browser, as well as matching JavaScript APIs: the Web Workers offering background and concurrent execution capabilities; a Web Storage allowing simple local data storage and manipulation in XML; and a Web SQL Database  providing the capability to perform SQL queries on large amounts of data stored locally and replicated from a server.
  • Mobile-oriented advancements (not yet finalised in the specs) including JavaScript APIs for Geolocation, Device and File APIs
  • Miscellaneous additions catering for the Semantic Web (microdata), security (cross-domain HTTP requests), and more.

To the above set of technologies standardised by the W3C we should add a domain that has sprung out of both proprietary or open-source efforts: high-performance JavaScript runtimes within browsers and JavaScript Application Frameworks. The latter extend the capabilities of the web, turning it into a full-blown client-side application platform much in the same way that UI and application frameworks like Qt or Gtk extend the “bare” Linux OS framebuffer. Such application frameworks include complementary JavaScript APIs, and rely on CSS3 to provide extensive sets of UI controls. Some mobile-specific frameworks (like Phonegap or BONDI, an offspring of the mobile operator community) go as far as providing additional device APIs for smartphone features like messaging or camera, while others provide a rich set of UI controls mimicking the native platform look & feel (more on this later).

Why the clash with Flash ?
There’s no denying that the capabilities brought forward by the emergence of the HTML5 “family” bring browser runtimes on a par with core capabilities of the Flash Player, which if adopted widely could make Flash redundant.

In the eyes of most mobile industry observers, the delays in bringing out a fully-featured Flash Player with acceptable performance on smartphones have played in favour of HTML5. Remember that, as of today, Flash Player v10.1 is only available for high-end smartphones that run the Android version 2.2 operating system. I would estimate that these represent only 1% of the overall smartphone shipments in Q2. This is a far shot from Adobe’s self proclaimed goal of having Flash shipping on 50% of smartphones by 2012 (see my previous article on this topic).

Figure: Smartphone Operating Systems – Q2 2010 Shipments share (source: Gartner, Google)

Company Browser / OS HTML5 compliance
Nokia Symbian S60 5th Ed. 7%
RIM Blackberry v5 0%
RIM Blackberry v6 (Torch)* 69%
Google Android v2.1* 50%
Google Android v2.2* 59%
Apple Safari for iPhone (iOS 4.0)* 62%
Microsoft IE Mobile (Winmob 6.5) 0%
Opera Opera Mini (on iPhone) 9%

Figure: HTML5 compliance of mobile browsers
[some notes on the methodology: HTML5 compliance was carried out using html5test.com. (*) denotes a WebKit-based browser. The Nokia Symbian S60 browser, albeit based on an old version of WebKit, scores poorly in HTML5 compliance tests. I could not test Mozilla Fennec, Palm’s WebOS browser, nor Opera Mobile.Opera Mini is a special case due to server-side rendering.]

Making things worse, Apple has stayed firm on its policy to not allow the Flash Player browser plugin on its iOS devices (iPhone, iPad and iPod Touch), preferring to rely on its in-house video streaming capabilities developed within its HTML5-capable WebKit browser core and QuickTime player. And to make things even more complicated, Steve Jobs’ “Thoughts on Flash” have played a key role in fanning the flames of the “Flash is dead, long live HTML5” fire.

Moreover, Google’s Android, Palm’s WebOS and, more recently, RIM’s Blackberry also embed web browsers based on WebKit that score very high in terms of HTML5 compliance, as can be seen in the table above.

Thanks to WebKit, half of the smartphones being shipped are poised to have the Flash-like capabilities brought by “HTML5” built into their browsers. However, let’s not rush in declaring Flash “dead” and Adobe a company in decline as a result.

Does HTML5 matter to Adobe ?
HTML5 is actually good for Adobe’s business. Indeed most of Adobe’s revenues do not come from Flash as can be seen by breaking down the Flash product portfolio::

  • The Flash Professional tool, is the authoring software for creating Flash content. It ships standalone or within the Creative Suite bundle. This is where Adobe makes its money as can be seen from the “Creative Solutions” BU share of the chart on the side (courtesy of Business Insider’s “Chart of the Day” series). Creative Suite also includes the massively popular Dreamweaver web design tool, and Illustrator, a vector graphics design tool, both of which which are now starting to incorporate HTML5/CSS3 design capabilities. Adobe has also hinted that Dreamweaver will be able to convert Flash timeline animations to Javascript/CSS3 code to render those animations in “HTML5” compliant browsers. This means that “HTML5” will not be a threat to Adobe’s main source of revenue. On the contrary, since there are few good commercial web design tools, the rise of “HTML5” will spur demand for Adobe products.
  • The Flash Player: the plug-in is free and is therefore represents  an R&D cost for Adobe. No impact there. One might argue that, if HTML5 were to totally eliminate the need for the Flash Player, it would the positively impact Adobe’s bottom line in the unlikely event the company were to lay off the entire Flash Player team 🙂
  • The Flash “Platform”: “auxiliary” products that rely on the Flash Player include the Flash Media Server and Flash Access product ranges, licensed to organisations that use Flash to deliver streamed video content (e.g. Hulu, Influxis, Brightcove). The “Platform” also includes the commercial Flash Builder IDE allowing the development of Rich Internet Applications (and the associated free and open-source Flex framework). As can be seen in the chart, these represent a minute proportion of Adobe’s revenue. As we will see further down, these products are not going to disappear overnight due to the emergence of HTML5.

However, HTML5 does put competitive pressure on the product management and engineering teams responsible for the Flash Player to out-innovate the evolutions in browser technology. Adobe points out that this is “business as usual for them” as –they say- it was never their intention to fully replace the browser altogether, but rather complement its capabilities with innovative features, and harmonise areas in which standards have been implemented in an inconsistent fashion across browser runtimes.

As an engineering-driven company, Adobe aims for Flash to stay one step ahead of HTML5 technology implementations, as it already is today in numerous areas. Indeed, an agile R&D division within a single corporate entity will always be faster than a “snail driven by a committee” as the W3C HTML5 spec bodies have been dubbed by some.

Some areas where Adobe is pushing the envelope for the Flash Player include 3D rendering with hardware acceleration, concurrency support, IP TVs and peer-to-peer media delivery. The latter is an interesting transposition of the file-sharing P2P concept; imagine tens of millions of users watching the same live video coverage of the opening ceremony of the 2012 Olympics in London. No server farm or CDN today is capable of sustaining such a peak demand. By allowing instances of the Flash Player across millions of peers to share chunks of the video stream at the edge of the network could be the answer to the problem.

Beyond innovation, another aspect to factor in is that HTML5 is still in its early stages of implementation across browsers, with Microsoft’s uber-popular Internet Explorer browser today lacking any form of HTML5 support whilst representing close to 60% of the web user base (see chart below). Even with the IE9 beta improving HTML5 support and other browsers consistently gaining market share it will still take some years before HTML5-capable desktop browsers dominate the installed base. This will justify the existence of Flash in the desktop browser space for years to come and give some leeway to Adobe’s engineering teams in designing more innovative capabilities.

Desktop browser market share

Company Browser HTML5 compliance
Microsoft Internet Explorer 9 beta 32%
Microsoft Internet Explorer 8 9%
Microsoft Internet Explorer 7 4%
Microsoft Internet Explorer 6 0%
Mozilla Firefox 4 beta 5 68%
Mozilla Firefox 3.6 46%
Mozilla Firefox 3.5 42%
Google Chrome v6 72%
Apple Safari v5 69%
Opera Opera browser v10 53%

Figure: Desktop web browsers users share and level of HTML5 compliance
(sources: wikipedia and test conducted with http://www.html5test.com)

Reality check: comparing Flash and HTML5 in key areas
So how is Flash vs HTML5 faring today? For review purposes we can single-out a few key areas of Flash and HTML5 competition, specifically display advertising, video delivery, games and application development.

Display Advertising: a slight advantage for Flash
One of the main use cases for Flash (and big source of annoyance to web users) is display advertising. “Display” adverts are animated banners that appear at the top, side or overlaid in front of the web content you. As annoying as they may be, display ads are a necessary evil for the online world since they represent 40% of the revenues that the digital content and e-commerce ecosystems live on. Even Google uses Flash in its DoubleClick Studio rich advert SDK for advertisers.

Some have said that because HTML5 will kill Flash, those annoying ads will disappear. I would rather think that they may be replaced by equivalents designed in HTML5/CSS3, with the caveat that they may look crappier in most of today’s browsers than their Flash counterparts, as can be seen from these examples.

Indeed a point often overlooked is that today’s HTML5 graphical rendering capabilities are at the level of what Flash capabilities were some years ago and CSS3 transforms allowing to design good “eye-candy” are inconsistently supported across browsers. Therefore I would argue that advertisers will hold back from using “HTML5” for display ad creation in the medium term. The lack of proper HTML5/CSS design tools will also delay this technology adoption by design agencies and creative professionals especially within  industry circles where Flash is deeply entrenched.

On mobile devices, the situation will be no different. The blue legos now seen on iPad and iPhones may soon be replaced by HTML5 counterparts; or even by iAds. However, as of today, Apple is the only company creating iAds (in the process levying a hefty ad tax) and is reported to be struggling with the demands of advertisers with its in-house HTML5-based ad creation tools and technologies.

Video Delivery: advantage for Flash
Another area in which “HTML5” has been touted a “Flash killer” is online video delivery. Let’s have a look. As far as basic video playback is concerned, Flash and HTML5’s <video> tag provide the same capabilities, so why not ditch Flash and avoid to end users the (relatively minimal) hassle of installing a plugin?

The situation is not as simple as it sounds as the various browser vendors do not yet all support the same video codecs. On one side, Apple and Microsoft are proponents of H.264; Google is pushing its opensource WebM codec (formerly the proprietary VP8 codec that it inherited through the acquisition of On2/Sorenson); and Mozilla and Opera by default supporting the free and opensource Ogg Theora.

This poses a challenge to online video publishers like YouTube since they then have to re-encode their content multiple times to support each codec.

To end users, this means that videos may not be available in the format supported by their browser. Flash on the other hand, even though it requires videos to be packaged in the FLV container format (not to be confused with encodings like H.264), is available across all desktop browsers and is used as a reliable fallback by “HTML5” web developers i.e. for the 50% or so of IE end-users whose browser can’t render the <video> tag.

Furthermore, the Flash Player supports advanced capabilities required by online publishers such as DRM protection (crucial for pay-per-view business models) and picture-in-picture overlay of multiple video sources with alpha-blending (e.g. for e-learning or overlay of contextual adverts). These capabilities may not be offered for years with the <video> tag in HTML5 browsers.

Casual Games and Visualizations
Flash is the technology that powers some massively popular “casual games” (such as Zynga‘s Farmville or Mafia Wars) played by millions of Facebook users worldwide. It also powers numerous other Facebook applications. There was earlier this year a rumor that Zynga was converting its titles to HTML5 to be able to run on the iPhone and iPad. This turned out not to be true, as it announced at Apple’s WWDC that it had ported Farmville to the iPhone as a native app; which may be interpreted as a sign that “HTML5” was not up to the task.

farmville.320x480-75 Another area in which today Flash is massively popular is that of visualizations and generative art. There is a large and enthusiastic community that has turned Flash animation into a true art form. Artists like Erik Natzke or Yugo Nakamura (of the Tha agency) are prominent examples of this community. To date, I have not seen any such artistic usage of “HTML5” technologies.

Other “HTML5” demos that have received a lot of media attention are Google’s “bubbles” doodle earlier this month, its experiment with Arcade Fire or a port of Quake to JavaScript using GWT. However, I do not yet see casual games developers or visualization artists migrating “en masse” away from Flash. This may be explained by the fact that those experiments in “HTML5” remain CPU-intensive and RAM-hungry (more than Flash in most cases), while designer-grade tools are lacking, and the fragmentation between browsers makes Flash a lot more dependable.

Applications Development: a draw
Web app development is another technology domain where the HTML5 family of technologies has been contending with Flash.

We have seen earlier that “HTML5” provides most core capabilities needed to run local applications, including code execution, storage and access to the screen. These core capabilities are now complemented by a flurry of web application frameworks that rely on JavaScript / CSS: DoJo, JQuery, MooTools and Sproutcore, to name a few. Google’s Web Toolkit (GWT) represents a particular case since it is a framework + tools package that allows to code a web application in Java and convert it to JavaScript for execution in the browsers (note how Gmail, Buzzz and other Google apps are built with GWT).

More recently, these frameworks have been forked into mobile variants: JQuery Mobile, Sproutcore Touch and Sencha Touch. Sendra is actually a case in point: the developer company raised $14 million in venture capital, a testament to the significant size of the business opportunity, and has jokingly proclaimed “The End Of Native” (see photo).

This abundance of JavaScript frameworks may be encouraging, but also represents a dizzying array of choices for the developer. This diversity limits the degree of industry-wide code reusability and fragments the pool of Javascript app developers into vertical niches.

This diversity further plays in favour of Adobe’s own web applications platform AIR (a sibling to the Flash Player) and the associated Flex framework, which uses the Actionscript programming language and allows XML-driven UI design through its MXML language.

In my own experience, seasoned developers find ActionScript and MXML a much better programming paradigm than Javascript frameworks in most developer aspects; code reuse, team productivity, tools support, debugging and ease of UI design.

In conclusion, the momentum behind web applications thanks to “HTML5”’s core capabilities and associated frameworks may seem unstopable, especially as it is driven by technology behemoths like Google and a large enthusiastic community. However this optimism is mitigated by the lack of developer productivity and the rising popularity of Adobe’s application development technologies.

What of the Future ?
Based on the earlier analysis, Flash is far from dead today. There are many cases in which Flash will continue to offer a better alternative (worst case a very useful fallback) to “HTML5” technologies due to the fragmentation in new web standards browser support.

To the question : “will HTML5 kill Flash?” there is no single answer. It all depends on which use case is considered and in what timescale.

On the desktop front, it is the lack of HTML5 capabilities in IE8/9 and their immaturity in all other browsers, that will secure the future of Flash in the medium term. At the same time, Adobe is under pressure from Microsoft, Google and Apple who are betting huge R&D budgets in the development of HTML5-capable browsers and who should be able to out-innovate Adobe in the longer term.

On mobile, the Flash Player is still in its infancy, while WebKit-based browsers are sharply rising towards ubiquity (250 million and counting as of end 2009). This gives the “HTML5 camp” an edge today, especially in the area of basic video playback and mobile web applications for which numerous JavaScript/CSS3 mobile frameworks are available. Looking forward however, Flash may still better HTML5 on mobile for use cases like casual games and animated graphics given its greater dependability and its widespread usage today in those communities.

Where would you place *your* bet?

– Guilhem

[Guilhem Ensuque is Director of Product Marketing at OpenPlug. He has more than twelve years of experience in the areas of mobile software and mobile telecoms. Guilhem was a speaker at last year’s Adobe MAX conference. His favorite pastimes (beyond mobile software strategy!) include making his baby daughter smile and sailing his Hobie Cat with his girlfriend. You should follow Guilhem on twitter @gensuque_op]

  • Guilhem,

    What a great article, very well considered.

    Looking at the current deployments of Android 2.2 it does seem difficult to see a 200million unit deployment by 2012. Those numbers are projections from Strategy Analytics, not Adobe.

    If you remember though, once we got to scale with Flash Lite – we shipped ~500m units in one year (2009). It's very possible to achieve, assuming that the smartphone growth pattern, and platform evolution continues.

    So my expectation is that the numbers will grow reasonably between June 2010 and June 2011. Following that however, we should see huge growth over a short period – the hockey stick curve as before.

    As you point out, no-one knows how this will all evolve, our hope is that HTLM5 works out, our customers need it to and therefore so do we.

    Mark Doherty

    Evangelist, Mobile and Devices


  • Carmen Delessio

    Great article. One point is that there are several companies besides Apple making rich media ads for mobile. Medialets and Crisp wireless are 2 examples. They would say that great interactive mobile ads existed well before iAds.

    Medialets sample ad

    Crisp Wireless sample ads:

    Carmen Delessio

    Director of Mobile Solutions and APIs

  • sam

    Great article. I could read this three times!

  • Great post Guilhem! Well researched and thorough. By far the best I've seen to date regarding these topics.

    Keep up the great work!


    John Epperson

    President, Ruxter Mobile

  • Will Law

    Re: "Flash on the other hand, even though it requires videos to be packaged in the FLV container format"

    Not quite correct. FLV is just one of the containers supported by Flash. Flash can also play videos packaged in F4V, MP4 and MOV containers.


    Containers: http://en.wikipedia.org/wiki/Comparison_of_contai

    Flash video support: http://en.wikipedia.org/wiki/Flash_Video



  • Great piece! Must read for anyone dealing with the content business.

    Anyway, there's no doubt that flash will be outmarketed by html5 in the long run: flash, not Adobe. Adobe though, is way in a risky situation: if an open standard arise, open tools for development will arise too: ask people at Borland what they think of Eclipse.

    Thanks for posting

  • Guilhem,

    What a great article !!!

    This is the best one among what I have been read about 'Flash vs. HTML5'

    Thank you for broadening my eyes and knowledge.



  • Thank you all for the great feedback

    @Will : thanks for correcting me on that. he fact that Flash supports multiple container formats only reinforces my point.

    Not sure however whether the end-to-end solution with Flash Media server supports multiple streaming protocols beyond RTMP with all the bells-and-whistles like DRM and fine-grained playback control (tru, basic HTTP progressive download IS supported but doesn't have those bells and whistles)

  • As a developer, I believe that the prevailing technology flash/html5 is the one that developers choose to use more.

    Developers many time adopt a technology based on the tool kits and frameworks available to them that ease their work and shorten development time providing pre-built library templates for the most common primitives used in most programs such as GUI elements, data structures, algorithms and connectivity.

    Currently, it seems that flash has the upper hand on that especially in the GUI elements department.

    Although action script (flash programming language) is considered by many developers to be a "backward" language compared to C++/C#/Java, many times acting not as expected and requiring special tricks to perform as expected and to circumvent bugs in the platform (Javascript is not the most popular language in that sense too).

    But like you say big companies are investing much money in changing that. I expect that developments in GWT and JQuery might hint on what the future holds for us.

    Thanks for a great article.

  • First, Guilhem I want to congratulate you for the excellent article you've written.

    Although many people believe there is a war between Flash and HTML5 should know that is totally false.

    I think both technologies can coexist. And more than that, they should join, mix.

    Why not integrate Flash into the HTML5 specification? I've always thought that the best way is to add a tag called 'flash' or 'ria' where there is SWF content. It would be like the canvas tag, but would also be able to resize.

    That is the best solution that we think developers. Flash technology allows us, thanks to vector graphics, develop truly on any device.

    But what is the problem? Adobe does not want to publish her Flash Player with open license.

  • Aissen

    « and Mozilla and Opera by default supporting the free and opensource Ogg Theora. »

    Mozilla and Opera are onboard for WebM support since public launch.

    Their latests browser versions already support it.

  • @Aissen – thanks for pointing out that Opera and Mozilla are supportive of WebM. However at the time of writing I could not view any WebM encoded video on YouTube with my run-of-the-mill FF3.5 browser … but sure it's gonna come.

  • I'm leaning towards HTML5.

    I've written a book about developing games in Flash, and I'm currently working on a quick reference to HTML 5. My next book will (probably) be about developing casual games using HTML5 technologies.

    Although I agree completely that HTML 5 and the related aspects of CSS and JavaScript are inconsistent and incomplete, I believe we developers have a vote.

    If we actually use these technologies (and write about them so others can use them) we can have an influence.

    I personally stay away from Flash as much as I can, because I'd rather support towards the future. Flash is great, but much of what we did with it no longer requires Flash, so I like having options.

    MSIE support is a bigger problem. If we choose to not support HTML5 because Microsoft doesn't want us to, we're letting them decide again what the future of the web will be. I don't want a webkit-only web. I don't want a Mozilla-only web. I want the major browser vendors to implement the standards they have agreed upon. Microsoft is moving from being the prominent voice in the browser to becoming an outlier. If they continue to be arrogant about web standards, either the new push to web standards will fail, or MS browsers will become irrelevant.

    Of those two outcomes, I vastly prefer that the standards prevail. I'm hopeful that Microsoft really chooses to get on that train.

  • Luca

    'To date, I have not seen any such artistic usage of “HTML5” technologies.'

    Although it is technically a port, Processing.js has done a lot of work in this area already. http://processingjs.org/

    There's plenty of brilliant artistic examples here:

    all using HTML5s canvas and Processing.js.

  • mhack

    I've avoided using Flash during the last 10 years and am glad for it now. I'm developing web apps using javascript/css/html5 and am enjoying it. Javascript is a fun and powerful language to work with, the main thing I miss is language support for modules/namespaces and I hear that is coming in later versions. Finally, I could care less about IE6/7/8 support for html5, most users these days can easily install and use a more capable browser.

  • @Andy @mhack Thanks for the feedback "from the trenches"

    Regarding IE, Microsoft are moving in the right direction (see the html5test score improving steadily in latest IE9 beta).

    However, even they can't control how quickly end-users upgrade to newer versions (esp. in entreprise).

    Maybe an easier update mechanism could help (like incremental upgrades ala Firefox).

  • robin.bakkerus

    I am a big fan since the start of Adobe's flex builder, long time ago.

    It reminded me of the good-old days of Delphi compared to struggling with C to build a webapp.

    I think that when it comes to build a complex business website with many pages and page-logic, the Flex builder is much productive then the html5 road.

    Things like: customizable components, event-handling, messaging, debugging, junit-testing etc are currently much more mature in Flex builder.

    So for now I would stick with Flexbuilder, for complex business apps targeted for the desktops.

  • My bet firmly lies with html5. It's certainly true that flash excels at some things over html5&co. However the more open (albeit somewhat fragmented) approach to a platform is good for the ecosystem of libraries and implementations. Also the fact that there's multiple browser competitors means that innovation rather then handed down by Adobe emerges in the form of outcompeting implementations, which is a very good thing.

  • Darren

    @Guilhem, I think Adobe will easily reach their target of being on 50% of shipping smartphones by the middle of 2012. Symbian will continue shrinking dramatically, nearly all shipping Android devices will have 2.2 and above, and Flash will be on Blackberry and WP7. By the way, Wowza Media Server is my preferred streaming software. It streams to Flash, iPhone, Silverlight and Quicktime from the one media file.

    @Florian, I don't see why there's a need to "bet" on either. Which technology you use should be based on what is the best technology for your purpose, taking all factors into account. And Adobe does have competitors which continually push it to innovate. Not just the obvious like Silverlight and JavaFX, but surely you must admit that Flash is competing with HTML5 too.

  • Frederik

    It really surprised me to read the term “SVG” only once in the whole article and the recent comments, and then in the general list of HTML5 markup components.

    I see there are two areas where HTML5 can really replace Flash player:

    * Video. Flash is currently the de-facto standard for web video players embedded in web pages. With the tag, this is no longer necessary. And this wasn’t the original goal of Flash, anyways, so it’s just logical to provide a native solution.

    * Vector Graphics. And this is the more interesting point: SVG was already named a “flash killer” long ago, but it failed to be one. Partly because Adobe acquired Macromedia and thus had no longer a reason to push an alternative to flash. But in the context of HTML5, SVG is back on the stage. Even IE9 will have decent SVG support, and Microsoft seems to really embrace this technique (despite them having their own Silverlight portfolio).

    I think that SVG has a large potential to get some of the Flash market share, e.g. when it comes to data-driven applications. Nevertheless, there is currently a lack of SVG authoring tools, especially with regards to animation and interactivity. So I see one possible step for Adobe in making Flash the de-facto SVG authoring application, if they would decide to add SVG export to flash.

    This would, as you said, be rather in favor of Adobe, as their USP is no longer the web runtime (which is replaced more and more by native browser implementations) but the authoring toolchain.

  • I've avoided using Flash during the last 10 years and am glad for it now. I'm developing web apps using javascript/css/html5 and am enjoying it. Javascript is a fun and powerful language to work with, the main thing I miss is language support for modules/namespaces and I hear that is coming in later versions. Finally, I could care less about IE6/7/8 support for html5, most users these days can easily install and use a more capable browser.

  • Hello, Well this is the eternal dilemma. Html5 flash … but the truth is that Adobe pushes too hard … Html5 still has not been as expected. It will take time but eventually will have to agree.

  • moose

    I started this weekend with my first canvas/js mini-game and believe me: it’s a total technical regress.

    The learning curve is extremely steep. First learn HTML and CSS. Then learn javascript. There’s tons off free libraries for javascript but for every step during development you have to pick one. For example when you need a simple bouncing effect; would you do it with jquery, mootools, jstween, tweenjs…? they all work fine but have different capabilities and non of them is (currently) as nice as Tweenlite. Some are best used for css others for the canvas…
    After that you’ll have to test on all browsers only to find out different things are not working on different browsers, which will consume more time. Time otherwise probably spend on design.

    The HTML5 demos look mostly like Flash 5-10 years ago.
    All visuals look crappy because Flash has a way to separate over half pixels, html5 doesn’t. This makes it look jaggy.
    To get sprites moving you will need more programs (I used Flash (!) and Zoe). The distance between designing and development get’s very big at this point.

    I started out as a designer and Flash helped me to start learning code step by step. Current young designers will have a hard time to do so in in HTML5 and most won’t make it, they’ll stick to design and will have to work in large companies. From an artistic point of view to keep things one on one, this is a disaster.

    So why would I switch to HTML5/canvas/js?

    Because the flash-guru’s are switching to HTML5. Mr. doob (Three.js) and Grant Skinner (Easel.js) are working on js libraries right now. These guys are the people who really make the difference in innovation and provide the tools. They did this for flash and are now doing it for javascript.

  • Ladies and Gentlemen,
    Well the endgame has one to an … end …

    Today Adobe announced that they were stopping all further development of the Flash Player on mobile, focusing their efforts on HTML5.

    They are laying off 750 people in the process, which no one should rejoice about.

    Official press release here: http://www.adobe.com/aboutadobe/pressroom/pressre

    Adobe is still keeping AIR for mobile (but for how long?), which is "interesting" given that at its heart, AIR contains the Flash Player.


Distilling market noise into market sense

What gets desktop developers out of bed in the morning?

desktop developer segmentation

Despite all the hype around the death of the PC and the enormous amount of media attention focused on mobile,…

Continue reading ...

A proven model for targeting IoT developers


  What if you could identify a handful of developer personas, or segments, each with a very distinct set of…

Continue reading ...

1000 skills: Amazon Alexa as a metaphor for the IoT developer community


Alexa is a centerpiece of Amazon’s Smart Home push, and quickly growing to become one of the most promising attempts…

Continue reading ...


Research on the app economy and developer ecosystems

Developer Segmentation 2014


The Developer Segmentation Q3 2014 report is the most sophisticated study of developer segments to date. The report delivers a…

Continue reading ...

App Profits and Costs


This research report examines the critical success factors for a profitable app, and how business and technology choices, such as…

Continue reading ...

Developer Segmentation 2013

Developer Segmentation 2013

The Developer Segmentation 2013 report delivers a needs-based segmentation model that actually works, with extensive profiling of the eight principle…

Continue reading ...