The power of mobile web browsers
summary
Live demo shows which mobile-browser APIs actually access phone hardware: Generic Sensor API (accelerometer, gyroscope, ambient light), camera via getUserMedia, Web Bluetooth (GATT battery service), Gamepad API, Network Information, Push/Notification, and the vibration API used to play a melody. Demos run on attendees’ devices over HTTPS, succeed mostly on Chrome/Android, fail or are limited on iOS; about 90 devices report support matrix and a surprising deviceMemory cap (8 GB). Demo app and repo links provided.
AI-written summary · about
chapters (17)
- 0:00Start
- 0:32Introduction
- 1:10What is PWACE
- 1:39What are the major points
- 1:57Speed
- 2:30Engagement
- 3:05Web or Native
- 4:08PWA vs Native
- 4:45PWA
- 5:20The main part
- 6:55What devices
- 9:17Network type
- 13:52Browsers
- 19:25Gamepad API
- 20:50Bluetooth API
- 22:00Media Devices
- 24:04Navigator Shell
related talks
44mJavaScript: What mobile browsers can do - 2020 revisited
49mMy browser does what?
45mBrowser API's: The unknown super heroes
45mMy Browser Does What
26mMobile HTML5: Device APIs and related APIs
13mEnhancing Mobile Experiences with Device APIs
36mThe internet of browsers
37mBrowser APIs: the unknown Super Heroes
