This document discusses mobile widgets and their development. Mobile widgets are offline-capable mobile applications that appear as icons in the device's apps menu and are built using HTML, CSS, JavaScript and AJAX. They are supported on platforms like WebOS and Android. The document outlines the benefits and challenges of mobile widgets, compares different widget platforms, and discusses how to build cross-platform mobile widgets.
4. What
Offline capable mobile applica0ons
Icon in the apps menu
HTML, CSS, JavaScript, AJAX
Invisible to the user
Meaning in WebOS and Android
Mobile Widgets
6. Positive
Well‐known technologies
Tools, Frameworks, IDEs
Web APIs
Low 0me‐to‐market
Por0ng
Applica0on Stores!
Only a few UI rendering engines
Easy to port from/to desktop
7. Negative
We s0ll need por0ng
Debugging
Standards
It's not na0ve, we know that..
Performance
Not for all kind of apps
8. Can Can’t
Applica0ons 2D games*
Web Mashups 3D games
Mobile Clients High CPU apps
Casual games Background apps*
13. Cross Platform Standards
For packaging
W3C Widget
Apple Widget
For Mobile Pla4orm Access
W3C Geoloca0on & MWI
BONDI
HTML 5
Google Gears
Nokia Plaform Services 2.0
ad.ag/jgwajg
27. Just for the record…!
• HTML based
– ACCESS NetFront Widgets
• Adobe Flash based
– Sony Ericsson’s Capuchin Project
– Nokia Flash (NFL Format) for S40
– Flash Mobile Packager
• XML and some script based
– Prosciu%o Project (Java ME)
– Yahoo! Blueprint
– Orange Djinngo
– Sun Java On Device Portal
31. Code Challenges
Performance
Dynamic app update
Pushing data
Por0ng
Using body class pa%ern
Using one CSS and JS per plaform
Data Storage
SQL
Key/Value
35. I think YES!
Define the UI
Define the app logic
Create the device detec0on framework
Port the logic and UI
Test & Debug
Package for every plaform
For OTA
Device Detec0on
Show Webapp or package delivery