Flash versus HTML5 - Wallaby and Swiffy conversion tools review
- Author: StatSilk
HTML5 (the new HTML/web-page language standard) is now widely touted as the replacement of Flash, and both Adobe and Google have recently launched tools to automatically convert Flash to HTML5. However, HTML5 will not suddenly be replacing all Flash apps for the following reasons:
1. Older widely used web-browsers do not support HTML5. According to the latest statistics the majority of Internet users are still using browsers that do not support HTML5. If you look at the enduring usage of the relatively ancient Internet Explorer 6.0 (released in 2001) you can see that it could take at least another five to ten years for the large majority of people to be using web-browsers which fully support HTML5. Currently even recent versions of the popular Internet Explorer and Firefox browsers have only limited or no support for HTML5.
2. Mobile devices do support HTML5, but also Flash - through the appstore. Android devices support Flash in the mobile browser up to Android v 4.0, but iPads and iPhones do not. The future of Flash on mobile devices and tablets is not in the web-browser, but in the appstore. These are Flash apps specifically designed for touch-screen interfaces. iPads and iPhones do support Flash-based apps through the appstore, and Android devices through the Google Play Store. Many of the most popular iPad and Android apps are Flash-based (you just don't know it, because it is not advertised anywhere). An example is the Flash game Machinarium, which when released on the iPad quickly became the number one paid iPad app.
At the moment Google Swiffy, released just a few months after Adobe's conversion tool, is the most promising of the two for more advanced Flash creations. This is because in addition to animations and graphics it can also convert Actionscript 2 and 3 into HTML5. Swiffy can convert Flash on the fly right in your browser and the conversion process is very fast - results often appear within seconds.
On the downside, Swiffy does not yet fully support Actionscript 3, and a number of common features cannot yet be converted. Swiffy is updated regularly though and the latest updates can be seen in the Swiffy release notes.
The Swiffy HTML output cannot be edited (or at least not easily), unlike the output from Adobe's CreateJS Toolkit.
Swiffy shows a lot of promise, and although it may not be able to convert very complex apps and games, with a bit of tweaking it can be used to convert almost anything.
(Updated March 2014) It appears that ActionScript 3 support is still much more limited than for actionscript 2, as conversion for an actionscript 3 app led to huge number of 'not supported' errors - including non-support for some very common libraries. I also tested Google Swiffy with several actionscript 2 Flash games, ranging in complexity from very simple to moderately complex, and the results were surprisingly good. Swiffy has certainly come a long way since 2012, when none of the Flash games converted would run.
In the latest version version all the converted ActionScript 2 games were actually functional, with just a few remaining issues:
- Flash components did not convert. For games this is not such a big issue (since they rarely use the built-in Flash components), however, it can be problematic for applications relying heavily on these components.
- Sound did not convert.
- Some graphical artifacts remained when going from one screen to another. This shouldn't be too difficult to iron out.
- It is slightly less responsive that the Flash version. Racing over chasms for example didn't always register, and instead of falling down the player just flew right over them.
Aspects which converted well are as follows:
- Converted timeline graphics and animations are exactly as in the original Flash version.
- The in-game mechanics converted well, aside from the responsiveness issue mentioned above.
- Keyboard interactivity worked fine.
In the latest version it is definitely feasible therefore to fully convert Flash applications and games, with a bit of tweaking to overcome some of the remaining shortcomings.
The Swiffy Gallery shows some interesting examples of what can be converted successfully, including two simple Flash games.
Adobe's HTML5 Canvas conversion and Google's Swiffy each have advantages and disadvantages so one or the other may be more suitable for your needs. The main differences are summarized below.
- Adobe Canvas: FLA files
- Google Swiffy: SWF files
- Adobe Canvas: editable HTML5 file
- Google Swiffy: non-editable HTML5 file
- Google Swiffy: decent ActionScript 2 conversion and limited ActionScript 3 conversion
- Adobe Canvas: included as part of Adobe Flash Professional CC
- Google Swiffy: can be used directly in the web-browser, or as an Adobe Flash Professional extension
On PCs, the lack of support for HTML5 means that Flash will likely remain popular for complex apps and games for at least some years to come. It will probably be replaced completely with HTML5 in other areas such as for advertising and animations. For mobile devices and tablets, Flash is supported in certain non-free web browser apps but is not likely to see widespread use. Instead it's future is in the form of apps. It is already a popular platform for building mobile apps because it can be distributed relatively easily across different platforms, including Apple's Mac OS X, iOS on iPads and iPhones, Google Android, RIM BlackBerry, Microsoft Windows and even TVs. Many people have apps on their iPhones and other devices developed using a Flash development platform without realizing it.
By the time that HTML5 becomes more widely supported on PCs than Flash, which may be around five years from now, it is very likely that Flash to HTML5 conversion tools will have become sophisticated enough to convert more complex Flash apps. HTML5 will need to evolve to be able develop the kind of complex apps that can be built with Flash today, and the evolution of conversion tools will go side by side with the evolution of HTML5 itself. Although many Flash developers consider HTML5 to be a step back, I see this as a small step back that will lead to a giant leap forward. It is too early to tell what the possibilities will be, but the future of interactive media looks as promising as ever.