W3C Widgets: for Web,
Mobile, or Desktop?
Apple Dashboard OpenSocial Nokia Widgets
Windows Sidebar Google Gadgets iPhone Apps
Google Desktop Google Wave Android Apps
Konfabulator Gadgets Widsets
Opera Widgets WidgetBox
You can connect all kinds of functionality to widgets by
injecting a JS API for it at runtime - and not just device
Did you know that Opera Unite services were W3C Widgets?
“W3C Widgets are better than websites
because they download only the data;
and not the core files.”
“Widgets are better than app systems
because you don't have to write 4, 5, or
10 of them. Just the one is enough.”
“And hundreds of thousands of web
developers already know how to create
- Peter Paul Koch
“A fundamental part of WAC is to ensure that developers have the
simplest method by which they can create applications for the long tail.
A key part of this is to endorse and encourage the use of technologies
which are based around open standards. WAC plans to initially use both
the JIL and OMTP BONDI requirements, evolving these into a common
specification within the next 12 months. The long term goal will be to
collectively work with the W3C for a common standard based on our
“I came here to ask if it's possible Google
Android will support W3C Widgets not
instead of but in addition to its own app
- a browser (Android WebKit will do perfectly
- a way of associating .wgt files with this
browser OR an installation mechanism
A Java server application in
the Apache Incubator.
Includes a W3C Widget
* “Wookie” is not a clever acronym. so if you spell it WOOKIE you’re shouting!
• Feature extensions beyond BONDI/DAP
• Widget and feature extensions for “other”
platforms. E.g. Android on TVs, kiosks,
uncategorizable gizmos etc
• Android+W3C Widget powered Chumby-