Design and implement a push notification service which will allow the WMF to send push notifications to browsers and mobile devices via vendor provided APIs.
|Resolved||LGoto||T146032 Define and implement a common push notification architecture|
|Open||None||T113125 Investigate using service workers to provide real-time Echo notifications in the browser (push notifications)|
|Resolved||• Mholloway||T163116 Define persistence backends for Push Notification Service|
|Resolved||MSantos||T246716 DBA review for Echo push notification subscription tables|
|Resolved||• Mholloway||T251431 Create .sql for Push Notifications tasks|
|Resolved||• Mholloway||T156513 Create technical plan for Push notification service|
|Resolved||• Mholloway||T244891 Create a chart reviewing and comparing existing open-source push notification server projects|
|Invalid||• Mholloway||T244893 Build a prototype push service|
|Resolved||• Mholloway||T247438 Estimate push notification volume|
|Resolved||• Mholloway||T249065 RFC: Wikimedia Push Notification Service|
@ovasileva I'm retagging this and putting into tracking. It's something we're likely to want to track if we ever want to add push notifications anywhere in the reading stack (which looks like iOS may want to do soon off the back of trending)
This task is about push notifications generally across the Readers platforms, and should be kept open.
I can't speak to all of the particulars, but I've added Roan and Joe to this task. Roan and Corey have been in discussion about technical architecture matters concerning push architecture as I understand. Web push is presently part of the FY 18-19 plan.
Jon, are you referring to the notion of something like scheduled jobs with Echo out to the message brokers (e.g., Mozilla, Apple, Google) or something to that effect?
Yes, but not specific to Echo, just with Echo as a consumer! An extensible Web push infrastructure would be incredible and open up a lot of possibilities to both WMF and volunteers. Exciting!