The Ugly Truths about HTML5 for Mobile Apps
summary
HTML5 apps hit real limits: WebKit fragmentation forces vendors to maintain multiple build systems and engine patches, leading to bugs and security holes; rendering and JS performance still trails native, as shown by Facebook’s HTML5 attempt that reverted to native. Web app packages vary by ~10 MB across engines, permissions and sensor access remain inconsistent, and Firefox OS introduces a limited-privilege app model while Servo in Rust (with Samsung backing) aims to change engine diversity but is not yet production-ready.
AI-written summary · about
chapters (11)
- 0:00Introduction and background
- 3:17HTML5 for mobile apps
- 6:58Challenges of HTML5 apps
- 13:15Permissions and security issues
- 16:38User interface and tooling problems
- 20:12Future of rendering engines
- 22:37Performance limitations
- 25:27Long-term app viability
- 27:57When to use HTML5 apps
- 30:56Mobile web vs app store
- 34:15Q&A
related talks
37mBuzz It For Real ! ... the tortuous road to Mobile HTML5 Apps
39mDoes The Browser Have A Future
43mSetting Disruptors to Stun!
53mBreaking Limits on Mobile HTML5
55mHTML for Mobile Web and Firefox OS
40mWeb Applications of the Future
07mMaximiliano Firtman interviewed at Velocity 2011
43mThe Mobile Web: MIA
