How to Make a Mobile Web App Better with Browser APIs
summary
A news-aggregator app migrated from Cordova to a native Android build, then moved back toward a Progressive Web App using Web App Manifest, Service Worker and Workbox. Offline-first uses IndexedDB to render ~200–250 articles in ~130 ms while fetching fresh data; network.effectiveType steers 2G/3G/4G behavior; Media Session and Web Share add native-feel UX; Credential Management and One‑Tap speed logins. A Workbox misconfiguration caused a 16 GB cache leak, and offering home-screen install increased active mobile users by about 10%.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:49Cordova to native app
- 6:39PWA install to home screen
- 10:29Offline with Service Worker
- 14:06UX with device APIs
- 16:34Sharing problem and solution
- 17:18Smart Lock and Credential auth
- 24:01New API integration challenges
- 26:55PWA versus native apps
- 27:37Q&A
related talks
31mMaking Mobile Web Apps Better with Web APIs
32mProgressive Web Apps
41mOffline Web Apps don't exist anymore!
38mProgressive Web Applications: The What, the Why and the How
47mThe (Awesome) Future of Web Apps
32mCross-platform Progressive Web Apps
53mProgressive Web Applications - The best of both worlds (App & Web)
03h 13mBuild your first mobile & desktop app as a Progressive Web Application
