- About the Survey
- The Audience
- Operating Systems and Browsers
- CSS and Presentation
- Rich Media
- Server technologies
- The Cloud
- Conclusions and predictions
In the introduction to this section of our report last year, we made the following observations, which are only reinforced by this year’s survey.
|For visual effects||1077||76.82%|
|For form validation||926||66.05%|
|For complex application interaction||683||48.72%|
|For Ajax communication with the server||818||58.35%|
|For visual effects||902||73.10%|
|For form validation||754||61.10%|
|For complex application interaction||520||42.14%|
|For Ajax communication with the server||659||53.40%|
Libraries and Frameworks
The big stories here are
- JQuery, already dominant last year with 63% of all respondents using it has increased strongly to a 78% adoption rate by respondents.
- Of the other libraries, only YUI (11.5% from 10.8%), and Ext (2.8% up from 2.7%) saw an increase in percentage use by respondents, Dojo stayed steady at 2.9%, and all others fell
- Despite these changes, the ranking from most used to least used stayed essentially unchanged
In addition to choosing from a list of th emost common libraries, we gave respondents the opportunity to name other libraries they use. Interestingly, despite gaining considerable coverage in the last year or so, the fully fledged application development focussed libraries Cappucino and Sproutcore each only were mentioned once. These libraries are much more geared toward desktop-like applications in the browser than more “low level” libraries like most of those listed above. It remains to be seen whether in subsequent surveys use of these libraries increases, or whether developers aren’t particularly interested in building desktop-like applications for the web.
Since our 2008 survey, HTML5 has gone from a promising, atalked about technology, to having quite wide support of various features in several contemporary browsers. It’s particularly well adopted in the browsers on mobile devices like the iPhone, and Android. To get a sense of how much the API features, as opposed to markup features of HTML5 are being used, we asked a couple of questions regarding their use in this year’s survey. Note to the pedants that we are aware that some of these APIs are not technically part of HTML5, and others have never been so, but we use HTML5 here as an umbrella term for new, browser based technologies.
Only fewer than 10% of our respondents say that they are working with these APIs. However, given their still limited support, and their only recent availability, that they have similar levels of adoption to SVG and Canvas is notable.
Of those APIs developers mentioned using, a little under a half (45%) use geolocation APIs, around a third (31%) client side storage, while web workers, websockets, drag and drop and the file API all are mentioned by a handful of developers at most.
Geolocation and client side storage are particularly relevant to mobile devices, so as we see mobile web use increase, and an increasing focus on optimizing for or targetting the mobile web user, we’d expect to see the use of those two technologies in particular grow strongly.
Do you use HTML5 APIs (geolocation, client side storage, webworkers etc)?
If so, which APIs do you use
|client side storage||40||31%|
|drag and drop||3||2.3%|
Like last year, we also asked some questions about developers’ scripting methodologies.
Developers also continue to adhere largely to the W3C DOM where possible, but the realities of different DOMs in different browsers mean most respondents take a pragmatic approach to this issue.
Do you strictly adhere to the W3C DOM, and avoid browser specific extensions?
|As much as possible||664||47.36%|
|As much as possible||613||49.68%|
While the percentage of respondents using them trails that using HTML5 markup, there’s still an impressive takeup of at least some aspects of HTML5 APIs, given how recent and still evolving these technologies are.
Next we’ll take a look at how respondents use embedded content like Flash, Silverlight, and other rich media formats which require often browser plug-ins.