Download to read offline
Uploaded byAnne Devia
Building performant and re engaging web apps with service
The document discusses the components necessary for creating offline-enabled and engaging progressive web apps, focusing on service workers, push notifications, and caching. It highlights the performance advantages of using new web features to maintain functionality in poor network conditions and re-engage users. Key topics include the importance of running quickly, compatibility across devices, and enhanced app scenarios using these technologies.
More Related Content
Similar to Building performant and re engaging web apps with service
Building performant and re engaging web apps with service
- 1. Building performance and re-engaging web appswith Service Worker (Ali Alabbas, May 7- 9 2018, Seattle) Learn about the building blocks of creating an offline-enabled and re-engaging Progressive Web App: Service Worker, Push, Fetch, and Cache. We'll cover each of these web features and how they provide performance benefits and help maintain functionality even under poor network conditions as well as how to bring users back via push notifications.
- 2. How to buildoffline-capable, performant, and re-engaging web apps 1. Why the web is a first-class platform 2. Why old web features didn’t succeed with solving offline 3. How to enable key app scenarios using new web features Offline & performance: Service Workers, Fetch, Caches Re-engagement: Push Notifications
- 3. Start and runreally REALLY fast! Work across a variety of devices, screen sizes, etc. Run over HTTPS Work offline / reliably under poor network conditions Can send push notifications Provide better device integration
- 4. Start and runreally REALLY fast! Work across a variety of devices, screen sizes, etc. Run over HTTPS Work offline / reliably under poor network conditions Can send push notifications Provide better device integration
- 5.
- 7.
- 8.
- 9. Exposed to JavaScript fetch(),Request and Response
- 10.
- 12. We need tosave Responses!
- 13.
- 15.
- 16.
Editor's Notes
- #4 A list of PWA principles Pwa means progressive web apps
- #6 there’s a lot of gap Native app capable of doing with web
- #7 A bunch of contributors talk to World Wide Web Consortium and came up to fill some of this gaps
- #8 App cache Normal langsung ke network
- #9 Ditambah fetch layer
- #10 how to we get back control to web devs
- #11 Better than web workers JavaScript that runs in the background
- #12 page usually send response to network Send request and get response Service workers, back to the page and get the response Dengan service worker pula lah waktu muat web menjadi lebih cepat. Teknologi service worker memiliki mekanisme untuk mengontrol asset yang akan di cache serta menyediakan custom permintaan ke jaringan sehingga dapat memberikan pengalaman akses secara offline bagi pengguna. Tetapi untuk dapat menggunakannya pertama kali pengguna harus mengakses website tersebut. Setelah semua asset ter-cache oleh service worker, sekalipun koneksi terputus pengguna tidak akan melihat gambar offline dinosaurus. Kira-kira seperti ini alur kerja service worker
- #13 so we can do something with those saved responses and going back to the page
- #15 Caches Balik lagi ke page