3 ms·
> you're just helping Android users And desktop users of Chrome, Firefox, and soon Edge (which has support implemented behind a flag).
by BHSPitMonkey 9y ago
> you're just helping Android users
And desktop users of Chrome, Firefox, and soon Edge (which has support implemented behind a flag).
- csharpminor 9y agoWhile true, the most compelling use-case for serviceworkers is still on mobile. Serviceworkers solve the problem of intermittent connectivity. They can patch the gap when a user drops a connection for less than a few minutes (e.g. when a user is mobile). Laptops and desktops still benefit, but less so because generally if you sit down to use one of those devices in an area of poor connectivity, you're going to run out of things you can do with your serviceworker's cached content pretty quickly. If you're developing a serviceworker, the improved experience will be most felt by mobile users.
- azernik 9y agoThat depends on the application. Some applications will run out of stuff to do after a few minutes offline, but others (especially where individual tasks are pretty independent, like Google Docs) can still be very useful for long periods, and can benefit from increased control of caching strategies.
- gramstrong 9y agoUnfortunately for Edge/Windows, in order to make the app installable it will have to be registered in the Windows Store. A small nuisance, and maybe a compromise that Safari/OSX could move towards, but still a pointless exercise that misses the point of PWAs.