# Notifications for SDK

## on the server
- client device tokens are set up and used (endpoint is created to register user with client device ID)
- We use FCM for sendong notifications based on Titles and subcribers to them

## on client end
- FCM needs to be used to receive the notifications
- eg: Troopod a vlient for Pushstart SDK will be using Firebase on the frontend to receive notifications.

## My Weeks task
- Create token service for FE - 1
- token registeration endpoint created.
- Moved out from subscription based firebase approach - 3
- No other option as firebase has only title based or user group based notification pushing.
- we can switch to group based notifications based on the number of users receiving the notification - limitation: "**The maximum number of members allowed for a notification key is 20.**"
- Handle token abusive - 2
- Update device token
- Add a update date to it (check for it if the date is less than 30 days, or treat it as stale.)
- Cool then!!!

## Alternatives
- Gotify
- FCM
- Pusher
- Custom: (websocket/long polling system)

# new task
- vaibhav- Annoucements, news-letters
- Siddharth - Threads, Reply on threads and stuff

# Task break down
- OneSIgnal RnD & POC. -1 day (also includes getting account from vaibhav)
- integrating onesignal and saving user tokens with expiry -1
- integrating the new notification system with threads 1
- adding notifications replies to a thread & reply on a reply - 1