Closing Panel: "HTML5 and Devices"
summary
Argues you must design content for many endpoints — desktop, phones, tablets, TVs and even digital signage — and recommends a content strategy that targets N internet‑capable devices rather than just responsive CSS. Recommends checking feature support with Can I use, reading MDN and contributing to WebPlatform.org; uses Netflix’s device bucketing approach to test thousands of Android variants; urges using Chrome DevTools, Edge Inspect or vendor debuggers to profile memory and battery because mobile limits break otherwise working web apps.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 7:25Future Friendly
- 10:02Selfaware devices
- 14:49Can I Use
- 17:52Internet of Things
- 21:10Connected Devices
- 22:37Mobile Devices
- 23:45Developing Markets
- 26:59Business Case
- 28:37Tensions
- 29:05Mobile Bell
- 30:18Mobile Network Operators
- 33:25Phones
- 34:05Android
- 34:55Hardware Requirements
- 35:55Basic Phones
- 36:31Spectrum
- 36:58Google
- 38:27Who will be driving standards
- 39:22CSS
- 39:48Prefixes
- 40:46Opera
- 42:15Web Standards
- 44:04Developing is Hard
- 45:21Web Dev Tools
- 48:19Automation
- 49:38Tools
- 50:52Devices
- 53:31Netflix
