Notifications are a powerful way to corral user attention.
We can add notification badges to any component in the MUI ecosystem.
Originating notifications:
For e.g. Tweet notifications or GitHub notifications there is typically a permanent instance of a BE to listen for events that cause a notification.
For us, without a permanent instance BE it's not immediately clear how the architecture should work.
For certain notifications we should be able to manage origination on the FE side, but for others
Dismissing notifications:
When users dismiss a notification where should that data be saved?
First thought is 3box.
If elsewhere is appropriate let's discuss.
onpaws
commented
4 years ago 
Notifications are a powerful way to corral user attention. We can add notification badges to any component in the MUI ecosystem.
Originating notifications: For e.g. Tweet notifications or GitHub notifications there is typically a permanent instance of a BE to listen for events that cause a notification.
For us, without a permanent instance BE it's not immediately clear how the architecture should work.
For certain notifications we should be able to manage origination on the FE side, but for others
Dismissing notifications: When users dismiss a notification where should that data be saved? First thought is 3box. If elsewhere is appropriate let's discuss.