SXSW 2010 Future15 : Rise of Mobile, APIs and Web Runtimes

Uploaded on


More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. It’s the Web (but not as we know it) The Rise of Mobile, Web Run-Times and APIs Daniel Appelquist (@torgo)
  • 2. The (mobile) Web Today • 28.6% of (U.S.) mobile subscribers using the mobile browser (Comscore) • Developers defecting from App Store to HTML5 (ZDNet) • Apple: 40%, Nokia: 16%, Samsung: 10%, Motorola: 7.6%, HTC: 5%... (AdMob) • “Mobile Touch Web” Growing:(Taptu)
  • 3. but...
  • 4. • You can’t access device information (location, contacts, camera, etc...) • You can’t build rich interactivity • User needs to be connected in order to get to the Web • User interface is clunky (launch browser, go to bookmarks, etc...) • No (easy) way to monetize webapps
  • 5. Interactivity & Graphics • Canvas • SVG
  • 6. W3C Widgets • Package up a web application using a well-known format (“P&C”) • Download and install (“install event”) • Specify required permissions (“WARP”) • Run in a “web runtime” environment • Automatic Updates (“Widgets Update”) • Cool open source implementation (Apache Wookie - • Real deployment environment: Vodafone 360; Nokia widgets; Opera
  • 7. Widgets and HTML5 • Widgets can use HTML5 • Widgets is a different take on off-line from HTML5 Appcache • “HTML5 Apps”* WebApps written in HTML5 packaged up as Widgets • Use Phonegap to package these as iPhone apps (for legacy purposes) *Peter-Paul Koch (
  • 8. APIs
  • 9. APIs (are sexy)
  • 10. Web Location: the W3C Geo API • Based on original input from Google, working group also included Mozilla, Opera, Microsoft and Vodafone • Work is complete, already embedded in shipping browsers: iPhone, Firefox 3.5+ • 21 Commerical services identified using it • Examples: Google Maps, Local Search, Flickr, Travelocity,, etc... • Many other sites using Gears Geo API
  • 11. Why is Location Sexy? • Because you can find Burger King • Refine search • Add location to any Web App • Apps like Gowalla are already on the Web (
  • 12. W3C Device APIs • Contact Book • Device Interface • Calendar • System Info & Events • Filesystem • Gallery • Capture Audio / Video • Tasks • Messaging • App Launcher
  • 13. Privacy Who gets to use all this data and for what purposes?
  • 14. • Appropriateness: Is the collection of information appropriate to the app? • User Control: How much control does the user have over how their info is used? • Notice: Is the user getting enough notice that information is being collected? • Consent: Is the user in control of decisions to disclose information? • Secondary Use: Is user consent required for secondary use? (e.g. ad targetting) • Distribution: Is information being re-transmitted to other parties? • Retention: How long is data retained? • Transparency and Feedback
  • 15. Location Privacy Design Principles
  • 16. Mobile Web Application Best Practices • Good advice on how to build great mobile WebApps now from W3C • We need “implementation reports” and feedback •
  • 17. OneSocialWeb • Open source, distributed platform for social networking • Based on XMPP and ActivityStreams + extensions • Enables social interactions, with access control, between social systems with no a priori knowledge of each other • Debuted at FOSDEM conference last month • • If you’re passionate about the social web, come join our community
  • 18. The Web is Evolving
  • 19. Thanks! Daniel Appelquist (@torgo)