Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In-App Notification System for User Updates & Admin Announcements #66

Closed
01bps opened this issue Feb 11, 2025 · 4 comments
Closed

In-App Notification System for User Updates & Admin Announcements #66

01bps opened this issue Feb 11, 2025 · 4 comments

Comments

@01bps
Copy link
Contributor

01bps commented Feb 11, 2025

There is no notification system for users. Admins cannot send updates, alerts or any info, and users do not receive any in-app notifications.
This feature will help users stay informed about any updates or announcements directly within the app.

Proposed Solution:

  • Bell Icon (🔔) on the top right to show unread notifications.
  • Dropdown Notification Panel (without page reload) to display messages.
  • Admin Notification Sender inside the same page, allowing individual or global notifications.
  • Database Storage to track notifications per user. We can flush notifications after a week once the user reads them to keep the database lightweight.

Using a single database entry for global notifications (user_id = "all") will help keep the system lightweight while ensuring all users receive important updates.

@pradeeban , Is it relevant to our use case? If so, I would love to work on implementing this feature.

@pradeeban
Copy link
Member

@01bps Thanks for the report. What notifications do you consider? Given the minimalistic nature of the application, I do not see a rationale (at this point).

@01bps
Copy link
Contributor Author

01bps commented Feb 11, 2025

I remember reading somewhere in the discussions that review boards are involved here, so notifications could be useful for things like "Your recent upload was flagged for review due to XYZ reason."
We could also use them to notify users before maintenance downtime or when a new feature is rolled out.

That said, I get your point—most of it might not be necessary at this stage. Just thought I'd bring it up!

@pradeeban
Copy link
Member

Yes, in that discussion, we reached the consensus not to censor/moderate the uploads at this point (when the target users will be in the range of 10 - 25, with each user intentionally chosen). We may need to come back to this discussion again in the future when we have 100s of users.

@01bps
Copy link
Contributor Author

01bps commented Feb 11, 2025

Understood, I was referring to the IRB aspect mentioned earlier #4 , but I see your point. We can certainly revisit this when the user base expands.

I’ll go ahead and close the issue for now. Thanks for the clarification!

@01bps 01bps closed this as completed Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants