🪣 Improved notifications system & push notifications (Client)

[sachben91]

Context

• Currently, all our notifications are “subscription” based, which leads to a situation where users have several levels of subscriptions to manage such as 40 in the case of the Common account shown below:
  • As part of our implementation of a progressive web app, we want to be able to send push notifications to user with the aim of engaging them more and increasing user retention
  • Once we add push notifications for stake, as well as push notifications for community updates such as “trending posts” (not in scope), the number of lines that the user will have to manage to manage their notifications will become unsustainable
  • Moving to a simpler notification system, one where some choices are abstracted away from the user and made more global will provide a cleaner experience for managing push notifications
  • As part of V1 implementation of push notifications, we want to build the basics of a push notification system that enables the user to: Manage push notifications easily, and get push notifications on the bread and butter of common - discussions and replies.
  • Push notifications are downstream of the implementation of PWA. Users should be able to enable notifications on ios and Android
  • In V2 (not part of the scope for these tickets), we will be focussing on user engagement notifications aimed at increasing user retention and bringing users back to Common more regularly.
  • As part of this change, we will also be making some changes to how notifications work in Common, such as what subscriptions mean, this will be detailed out in individual tickets below
  • We also want to get our email notifications to a working state with no new features added, this will also be detailed out in a separate ticket

Detailed PRD Flowstate

Product Owners

PM: @sachben91 Designer: Jared Bell Engineers: @timolegros,

Push notifications for V1

Here is the list of notifications for V1 on Push notifications

• The notifications themselves, how they show up on ios or android, may need design input, these tickets can be created after engineering exploration on how push notifications are implemented

Tickets

• [ ] #6655
• [x] #6622
• [ ] #6625
• [x] #6627
• [x] #6628
• [x] https://github.com/hicommonwealth/commonwealth/issues/7610

[sachben91]

On the modal for Notifications, We will go with the modal that Knock provides, give that:

• We can implement our font in the modal
• The modal has a scroll so that the user can check their previous notifications

@burtonator is investigating both the above

cc @ForestMars

[sachben91]

We could potentially release notifications in two phase:

• In the first phase we can release in-app notifications - this would need working notifications along with the new modal and #6628 for managing items the user has subscribed
• The second phase can have the pwa notifications and the other notifications management screen
• Email notifications can also be in the first phase

cc @burtonator @CowMuon @timolegros @jnaviask

[burtonator]

@jnaviask @sachben91 I think as per the above request from Sachin that I should implement this:

https://github.com/hicommonwealth/commonwealth/issues/7705

but we only have one mention of the PWA portion of notifications - it's really the most complicated part though.

I'd like to work on that BEFORE the subscriptions screen because the work I did from last week is still in my head.