Implement Pinghub WebSocket client, to receive updates, regardless of the Push Notifications setting.
### Details:
Automattic/pinghub-android repository.How PingHub will benefit our users? GCM does the same job already, I don't really see the point of adding more complexity to the app.
We won't replace GCM with Pinghub for PNs.
Instead we want use it to keep the clients in synch with the server and use less REST calls.
I know we can use GCM for almost the same things we want to achieve by using Pinghub, but there are few key advantages with Pinghub:
cc @jleandroperez @dmsnell
and @mzorz (but probably you're already seen this).
So, we're going to replace all the REST calls for notifications with PingHub?
initially not all, but hopefully many :)
What is GCM?
Google Cloud Messaging (now "Firebase")
So, we're going to replace all the REST calls for notifications with Pinghub?
Almost all the REST calls could be easily migrated to PingHub. (When we'll be ready to accept and process incoming messages on the server).
I would say, the initial notes refresh, and pull to refresh, can use the REST API, at least in the first version of Pinghub integration. If everything works OK we can move all calls to PH in a second sprint.
Ok that would make sense to only have one way to communicate with the notification "server", my fear is having an extra complicated implementation for such a simple screen.
Closing as the Notifications Refresh project has reached to an end
Most helpful comment
We won't replace GCM with Pinghub for PNs.
Instead we want use it to keep the clients in synch with the server and use less REST calls.
I know we can use GCM for almost the same things we want to achieve by using Pinghub, but there are few key advantages with Pinghub:
cc @jleandroperez @dmsnell
and @mzorz (but probably you're already seen this).