Panel Discussion Day #1: PWA vs Native
summary
Discussion contrasts real tradeoffs: Gatsby ships pre-rendered HTML for fast load and SEO, Expo for web reuses React Native with built-in splash/safe-area handling, PWAs lose some native APIs (iOS notifications, photo gallery, contacts, calendar, certain camera/ Bluetooth gaps) and show inconsistent screen‑reader behavior across browsers. PWAs win for iteration speed, low data/slow networks, and distribution; native wins for deep engagement, complex gestures and guaranteed hardware features. Cordova-era webviews and Play Store/Trusted Web Activity limits surface as concrete obstacles.
AI-written summary · about
chapters (7)
- 0:00Start
- 2:05How Would You Define a Progressive Web App
- 5:37Progressive Web Apps
- 9:44Do You See Hope in the Future for More of this Functionality Being Exposed to Mobile Apps or Mobile Web Apps
- 13:17Accessibility
- 20:46Payments
- 21:07Bluetooth Api
related talks
11mNative, Hybrid, PWA? How to deal with it?
26mBuild it Once with Expo for Web: Create PWAs with cutting-edge browser functionality
34mI Can't believe it's not native - UX and performance with PWAs
56mPWA vs NATIVESCRIPT
37mThe Mobile Web Second Edition" First-Class Citizen on Your Device Now"
31mBreaking the Limits of PWAs with JavaScript APIs
54mOne PWA to Rule Them All
22mPWA Every Day Progressive Web Apps vs Native Apps