3 ms·
I read the post, then looked up ServiceWorkers and this progressive web app stuff, and it doesn't seem that useful. You don't have access to files, or hardware
by odbol_ 11y ago
I read the post, then looked up ServiceWorkers and this progressive web app stuff, and it doesn't seem that useful. You don't have access to files, or hardware (Bluetooth/sensors), or notifications, so what's the actual use case?
It seems like it's just a way to be able to make cross-origin requests in a browser. Can it even do that? Seemed like it had a bunch of security considerations that make even that not useful.
- rictic 11y agoService worker supports notifications: https://developers.google.com/web/updates/2015/03/push-notifications-on-the-open-web?hl=en https://developers.google.com/web/updates/2015/03/push-notif... The primary use cases for service workers today are robust offline support and notifications. More generally service worker gives you broad and very fine grained control over your app's use of the network. Service worker itself doesn't give additional cross-origin request abilities, except by giving more control over caching. Web Bluetooth is still a work in progress, but you can try it out: https://developers.google.com/web/updates/2015/07/interact-with-ble-devices-on-the-web?hl=en https://developers.google.com/web/updates/2015/07/interact-w... (disclosure: I work on this kind of stuff for Google)