Ad-hoc push notifications tool / interface
Target problem
Most Minds app users do not get frequent push notifications because they don't get daily engagement on their content. Because many are not reminded of Minds through notifications, they forget to check into the app daily.
Hypothesis
By sending more regular general push notifications (e.g. Watch Minds on Joe Rogan), we can remind many users to check into Minds daily.
What is the primary metric that this change is aimed to improve?
DAU, Check-ins
What counter metric will ensure that an increase in the primary metric is a positive for the product?
% of users with push notifications enabled / Minds has access to send them notifications
Size estimate
(Size estimate -- from Design + Dev -- required to deliver this change. Is just an estimate)
Acceptance Criteria
- API endpoint (restricted to only admins) to trigger ad-hoc push notifications
- API to support basic reporting of notification
- CLI for testing and/or manual triggers
- Abstraction of sender lists for future targeting support. Initial implementation to go to all devices
- Backend runner to subscribe to events
- Fields to support Title, Message, Link/URI
- Database to store (timestamp, author, title, body, uri, counter, status)
- Frontend to live in admin panel
Edited by Mark Harding