About the conference
FITC claims to be a conference for “Digital Creators” and its tagline for the Amsterdam edition is “Design. Technology. Cool shit.”. The audience was a blend of designers and developers, students, freelancers and design studios. The presentations covered areas from technical subjects on Flash, Flex, 3D and mobile development to talks about design and even business and marketing. There was also a keynote presentation from Adobe that covers the new developments in their frameworks and tools.Many important people from Adobe were also there giving presentations and talking to the members of the community. Including people from the FlashBuilder and Flex SDK program management team and people from the Flash Player engineering team.
I found that most people I talked to were more targeted towards Flash design and development, making web page designs and advertising campaigns for their clients. Judging by the well worked out mixture of presenters and the diversity of the given presentations I am sure that there were also a lot of Flex developers present but for some reason they were a bit harder to find, at least for me.
Flash vs HTML5
There were a lot of talks about HTML5 on the conference and as to whether or not the new capabilities of HTML5 will put Flash out of a job. The general conclusion was that this might eventually be the case but not in a near foreseeable future. Even though the new HTML5 canvas and CSS3 specifications will allow for a lot more elaborate user experiences in a browser this is still a very immature technology. A few of the things that should make you think twice before switching over to HTML5 for your application development are:- Browser support is still bad. Many major browsers are still not close to implementing all the new features of the HTML5 and CSS3 specifications meaning that the cool new stuff you implement might not even work in all browsers.
- Cross browser compatibility. Different browsers implement the new capabilities in different ways leading to you having to code around the differences to maintain a consistent user experience across different browsers.
- Performance. The different implementations of HTML5 canvas still require a lot of processing power so switching to HTML5 to support more mobile platforms is not a good idea yet.
- Tool support. In terms of development experience and productivity people have already started to develop nice new tools and APIs towards the new HTML5 and CSS3 specifications but there is still a long way to go.
No comments:
Post a Comment