Mozilla recently announced a new WebAPI for enabling mobile web applications to talk to device features. If that sounds familiar, then it should, as W3C and WAC have been developing similar APIs for a few years now. The scope of the Mozilla initiative looks, on first glance, to be almost exactly the same as that of DAP – including the APIs that the W3C DAP group have put on the “at risk” list.
This could of course be good news if Mozilla uses this as an opportunity to push forward on DAP specs that haven’t made progress for one reason or another (e.g. Media Gallery and Calendar). However, in some cases the delay hasn’t been lack of interest or effort, but simply waiting for other parts of the web platform to become stable (e.g. websockets and HTML5 device/navigator object). There has also been a lot of learning going on as to what the right design patterns are for these kinds of APIs (listeners versus callbacks, multiple versus single handlers, etc.) and what is an appropriate scope given the stability of different aspects of device hardware functionality.
In the comments on the post linked above Robert Nyman responded to criticisms that Mozilla was fragmenting the standards space:
“The idea is to collaborate with W3C and all players and together form a good solution, and not just dump it on them.”
However it would have been better to have made this completely clear at the outset rather than announce the WebAPI as if it were a completely green field idea and then handle the “WTF?” reaction. (A similar argument emerged in relation to Mozilla announcing what appeared to be a competing installable web application/widget format)
Of course this means I have to add some more boxes to my mobile web applications standards wall-of-bricks picture (click for the larger version):
“Please refer to http://xkcd.com/927/ and then adopt one of the 14 existing proposals.”