W3C Widgets are applications developed with web standards that can run across different mobile platforms using the browser engine. A widget consists of an index.html file, assets, and a config.xml file packaged into a .wgt file. Widgets take advantage of HTML5 features like the Application Cache, WebSQL storage, and local storage. They can run on browser runtimes including Opera Mobile, Widgeon, Windows Mobile 6.5, Nokia Qt Web Runtime, and Apache Wookie. The W3C is working to define JavaScript APIs for contacts, calendar, media capture, and messaging to provide more capabilities to widgets.

1. W3C Widgets
Bruce Lawson / Over The Air / London / 10 September 2010
Apps – with added Web Standards goodness!

3. “…the browser run-time is perfect…you’re out
of writing for Windows Mobile, Android, S60, each
of which require testing...we want to abstract
that.
All the cool innovation is happening inside the
browser – you don’t need to write to the native
operating system anymore.”
Mobile Entertainment Market, June, 2009

4. W3C Widgets – application development filled
with web standards goodness,
using browser engine as platform

5. Anatomy of a widget
index.html, assets + config.xml,
zipped and renamed .wgt

7. Features depend on browser
HTML5 App Cache, WebSQL storage, HTML5
local storage, <audio>, <video>

8. Widget runtimes
●
Opera desktop, Opera Mobile, Opera for
Devices (including TV)
● Widgeon
●
Windows Mobile 6.5
●
Nokia Qt Web Runtime
●
Apache Wookie
●
Aplix Web Runtime
●
Lots of Vodafone distros

9. What's next?

10. <device>
(HTMLnext, WHATWG)

11. W3C DAP
(Devices and Protocols Working Group)

12. Defining JavaScript APIs:
● Contacts (access address book)
●
Calendar API
●
Media Capture API (programmatic access to
camera/microphone)
●
Messaging API (email/ SMS)
http://www.w3.org/2009/dap/

15. www.opera.com/developer
bruce.lawson@opera.com
twitter.com@brucel