Panel 6: Privileged access
summary
PhoneGap shows packaged web apps can ship to stores, run from file://, and call device APIs (camera, GPS, contacts) but battery polling in one PhoneGap prototype actually drained the battery; offline quota still sits around 2–5 MB per origin so big games must delta-download levels. Firefox OS introduces three privilege tiers and a marketplace review for high‑risk APIs; Chrome experiments use Cordova and an Appmeter/Confetti toolchain to emit multiple manifests. Runtime permissions, USB device IDs, and a manifest + white‑list update model are the unresolved pieces.
AI-written summary · about
chapters (42)
- 0:00Introduction
- 1:00Privileged applications
- 13:35Questions in moderator
- 14:57No timely access
- 15:32User media
- 16:15Facebook example
- 16:47User acceptance
- 17:25Installing apps
- 18:12Browser interface
- 19:36Widgets
- 21:13Browsers
- 21:45App compatibility
- 22:30Web APIs
- 25:04Offline
- 25:35UX
- 25:57Education
- 27:15Power of the web
- 28:45Complex problem
- 30:35Request access
- 31:13Different levels of privilege
- 32:36Open marketplace API
- 33:11App permissions
- 35:27Trustworthy apps
- 36:20Natively integrated experiences
- 37:10Contact manager
- 38:32granularity
- 39:15api
- 40:46granularity of permissions
- 43:18permissions model
- 43:52packaged apps
- 44:15phonegap
- 44:25cross browser support
- 45:20nodebased servers
- 45:40fullscreen
- 46:59banner
- 47:11permissions
- 47:58storage
- 48:51last words
- 49:06Adobe Air
- 49:27Chrome App Store
- 49:39API Stack
- 50:18WebRTC
related talks
43mAfter HTML5: Mobile Device APIs and PhoneGap
49mDevice/network API panel
45mThe Nightmare Behind The Cross Platform Mobile Apps Dream
39mDevice APIs
44mMobile Penetration Testing Hybrid
31mThe power of mobile web browsers
04mJonathan Stark interviewed at OSCON 2010
25mAbusing Firefox OS and HTML5 games for fun and profit