Widgets and Mashups for Personal and Institutional Technologies


Published on

Talk at KMI on roadmap for multi-device web applications and relationship to education

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Widgets and Mashups for Personal and Institutional Technologies

  1. 1. Widgets and Mashups for Personal and Institutional Technologies Scott Wilson University of Bolton, UK
  2. 2. Scott Wilson• Researcher at the Institute for Educational Cybernetics at the University of Bolton• Assistant Director of Centre for Educational Technology and Interoperability Standards (CETIS)• Member of the W3C Web Applications Working Group, contributes to the W3C Widgets family of specifications• Committer on the Apache (incubating) project Wookie which implements the specifications• Currently Scott works on two EU-funded projects, OMELETTE and iTEC, both of which are using W3C widget technologies to create flexible mashups
  3. 3. Widgets and Mashups forPersonal and InstitutionalTechnologies
  4. 4. Suddenly,lots of devices
  5. 5. Not just devices, either, gizmosA Gizmo, unlike a Machine or a Product, is not efficient. A Gizmo has bizarre,baroque, and even crazy amounts of functionality … Its a cellphone, a webbrowser, an SMS platform, an MMS platform, a really bad camera, and anabysmal typewriter, plus a notepad, a sketchpad, a calendar, a diary, a clock, amusic player, and an education system with its own onboard tutorial that nobodyever reads. Plus I can plug extra, even more complicated stuff into it, if I takea notion. Its not a Machine or a Product, because its not a stand-alone device. Itis a platform, a playground for other developers. Its a dessert topping, andits a floor wax.- Bruce Sterling
  6. 6. Personal Technology In The Age of Gizmos• Everything is internet-connected, has a browser, a GPS, accelerometer, compass, multi-touch screen, whatever…• But for display can have anything from a 320x240 pixel feature-phone screen to a 50” plasma screen• And it can run Apple IOS, Android, Bada, WebOS, Windows, Nintendo, Google TV, YouView, QT, Blackberry OS, Linux…
  7. 7. Complexityall these devices, operating systems and feature sets isan amazing opportunity forinnovation…… and a huge headache foranyone involved in IT forInstitutions
  8. 8. Web on Everything• W3C Standardising core aspects of the open web platform – Widgets – Device APIs – HTML5 – Device Independence and Content Adaptation – Multimodal Access – Web TV
  9. 9. W3C Widgets HTML config.xmlJavaScript CSS Icon.png mywidget.wgt
  10. 10. W3C Widget ApplicationsDesktop Widgets Website Gadgets Mobile AppsInstallable Web Apps TV Apps Car AppsConsole Apps Browser Extensions Portlets
  11. 11. “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 dont 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 widgets.Its just HTML/CSS/JavaScript, after all.”- Peter Paul Koch
  12. 12. Device APIs: Adding Device Capabilities to the Web• Contacts • Network Information• Calendar (roaming…)• Battery status • Systems info (CPU…)• Media Capture (mic, • Permissions camera…) • Gallery• Messaging (SMS, • Launcher MMS…) • Tasks • Privacy JavaScript
  13. 13. Device APIsJavaScript HTMLnavigator.device <input .capture.capture type="file" Image(success, accept="image/* error, { limit: " id="capture"> 1 });
  14. 14. Open Web Application Stacks• WAC: Widgets + DAP + Mobile = mobile open web applications• CME: Widgets + Media = enhanced music content• Web TV: Widgets + DAP + TV = open TV web applications• Opera: Widgets + Extensions = browser extensions• Omelette: Widgets + Telco APIs = telco mashups
  15. 15. Why is all of this interesting?• Simple, embeddable, personalized, contextual…• Scenarios: – Cross-device applications – Multi-device applications – VLE -> MUPPLE
  16. 16. Cross-Device Apps
  17. 17. Multi-Device Planning and monitoringFieldDataCapture Reading and reviewing Writing
  18. 18. VLE - MUPPLE
  19. 19. The Social Life of Widgets• Widgets living with other Widgets• Widgets talking to other Widgets• People talking about Widgets• Institutions giving people Widgets• People giving each other Widgets
  20. 20. Widgets LivingWith OtherWidgets
  21. 21. Widgets TalkingTo Widgets(*potentially. These sites don’t use them, but areexamples of what you might do)
  22. 22. People Talking About Widgets Top 5 apps that help you find more and better apps
  23. 23. Institutions Giving People Widgets
  24. 24. People Giving Each Other Widgets Flatpack
  25. 25. The Road Ahead
  26. 26. Now and next• DAP WG commodifying today’s device capabilities• HTML5 everywhere• Inter-widget mashups still experimental• Widgets standardised across more platforms• Platform wars: native vs web• “Appification” of existing platforms: whiteboards, TV• VLEs with an app• BasicLTI and widgets• Widgets for core institutional (admin) services• Cross-device applications using adaptation techniques• Bump-sharing apps between mobiles
  27. 27. 2-5 Years• More device form factors, but all fundamentally based on web technologies• New hardware capabilities for devices exposed to web applications then commodified by W3C• VLEs made of widgets; mashups of widgets a common way to build applications• Multi-device applications exposing fundamentally different collaborating capabilities (e.g. “second screen” technology)• Social App Sharing - by twitter, email, buttons…• Federated social web?
  28. 28. Challenges and Opportunities• From VLE to PLE … or from PLE to VLE?• Widgets as social objects - sharing, discovering, co- creating• Widgets talking to platforms• Balancing act between adopting standards for the long term, and delivering functionality now• Designing for “any device”• Making personal mash-up building easy, fun and worthwhile
  29. 29. Thanksscottbw@apache.orgscott.bradley.wilson@gmail.com@scottbwhttp://scottbw.wordpress.com