Make notifications server-driven #3
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
foravo/milestone-proof-20260519050317#3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Imported from GitHub issue
StanfordCS194/spr26-Team-22#99.Source: https://github.com/StanfordCS194/spr26-Team-22/issues/99
Original author: @nriedman
Original state: open
Summary
Right now, remote notifications are simulated with on-device local notifications. Moving forward, we need to build out our server driven infrastructure.
Imported from GitHub issue comment
StanfordCS194/spr26-Team-22#99:4458270908.Source: https://github.com/StanfordCS194/spr26-Team-22/issues/99#issuecomment-4458270908
Original author: @yusabd
This is necessary for invitations to function, but weekly check ins and nudges are fully functional locally, with a simulated debug mode and active production mode. Will still make all of them server-driven.