I like this, but it needs to be tightly scoped.
Our first priority is getting the push notifications going for Android, cause that unlocks brand new functionality.
Our second priority is a PR to message bus that enables centralizing of message bus polling without turning message_bus.js into a âsoupâ of completely hard to understand and debug code that falls back super cleanly.
And before we do any of this, there are critical items on the 1.4 release list that are not doneâŠ
Oh my 
Canât wait to try this out!
(and 10 seconds later have iOS users complain that theyâre not supported. Come on Apple!)
Hmmm the Push API isnât available until FireFox 42, Iâll wait till it is released first before integrating push notifications for FireFox. In the mean time, Iâll update my PR to account for different browsers.
This is not (or at least no longer) true, see the clients.claim() API: https://slightlyoff.github.io/ServiceWorker/spec/service_worker/#clients-claim
Good news from Microsoft land: service workers and the push api moved to High Priority in the roadmap for Edge.
Big thumbs up for push notifications. Weâre currently trialling Discourse to replace PhpBB for CAMRA (170,000 members) and Iâve been a fan of Discourse - having used StackExchange for years.
The single biggest requirement for the replacement system is so smartphone and tablet friendly but Discourse isnât sadly ticking all the boxes. Itâs better than PhpBB but maybe not enough for us to recommend 
I think that is a bit unfair, I use Discourse quite extensively over mobile as do many others, we have spent enormous amounts of engineering effort making sure the mobile story is great. To add to that you can do everything over email (reply, like, open topics etc) which also captures a bunch of use cases.
We plan to add support for push notification in a shell mobile application. However, the current experience is far superior to many other mobile sites I have seen and use. You achieve much of the notification over email anyway.
Iâm not sure why itâs âunfairâ. I like Discourse but to say itâs as mobile friendly as it could be would be ignoring the truth. The stakeholders in our project are not IT specialists and like the rest of the world, have come to rely on their mobile phone. So when they say âwhy doesnât it work like this?â, weâre immediately on the back foot defending the fact that Discourse is a web application and not a native one. Iâve asked whether I can start a separate thread on, for us, will be a key decision point.
Iâd keep an eye on ember-service-worker · Issue #45 · ember-cli/rfcs · GitHub and GitHub - html-next/skyrocket: Ambitious applications arenât single threaded. as well.
Massive support signal from Google last week: the 2016 Foundersâ Letter mentions Progressive Web Apps as one of Googleâs two investments in the mobile web:
We also continue to invest in the mobile web [âŠ] Over this past year, Google has worked closely with publishers, developers, and others in the ecosystem to help make the mobile web a smoother, faster experience for users. A good example is [âŠ] Progressive Web Apps (PWA), which combine the best of the web and the best of appsâallowing companies to build mobile sites that load quickly, send push notifications, have home screen icons, and much more.
Service Worker support is the cornerstone of PWA support.
As a Developer Advocate at Google helping with PWA and AMP efforts, please let me know if thereâs anything we can do to help flesh out SW support - which I do see running at https://meta.discourse.org when I use a mobile UA.
EDIT: Added another relevent video.
Recent talks from Google I/O 2016:
A good potion of this walks through the âofflineâ capability.
These videos are long, the first is 45 minutes long so - do yourself a favour and use the Video Speed Controller extension in Chrome.
Good news for Service WorkerâŠ
The Fetch API MS Blog post link: Fetch (or the undeniable limitations of XHR) - Microsoft Edge Blog
to continue?
