Notifications and Updates

Product Requirements Document (PRD) - Notifications and Update Features

Novu (Service used for notifications)

https://novu.co https://docs.novu.co/quickstarts/nextjs

Push (web3 native notifications and stream)

https://push.org/docs/

Arianee dMessages

https://docs.arianee.org/docs/arianee-js-messaging

TL;DR

Implement enhanced notification and update features to improve user engagement in a content-focused app. Notifications inform users of various activities like pass received, pass redeemed, etc., with an optional CTA. Updates alert users to changes in the interface, particularly in a content space by an organizer they follow.

Goals

Business Goals

1. Increase user engagement by providing timely and relevant notifications.
2. Drive higher interaction rates with content spaces through targeted updates.
3. Enhance overall user experience, leading to increased app usage time.

User Goals

1. Stay informed about important activities and updates in the app.
2. Easily navigate to relevant sections of the app through notifications and updates.
3. Reduce information overload by receiving only pertinent notifications and updates.

Non-Goals

1. Overloading users with excessive notifications.
2. Implementing complex notification customization settings at this stage.

User Stories

1. As a user, I want to receive notifications about activities like passes received, so I can stay informed.
2. As a user, I want the option to act on notifications through a CTA, for a seamless experience.
3. As a user, I want to be alerted to updates in content spaces I follow, so I can view the latest content.

User Experience

1. Notifications:
   • Display sender's avatar and name.
   • Show the type of notification with i18n support.
   • Include an optional CTA that redirects to relevant sections, like the pass section.
   • Update notifications dynamically; remove CTA post-action and update text.
2. Updates:
   • Use a marker stored in cache to indicate new updates.
   • Highlight updates like new content in followed spaces.
   • Provide clear visual cues in the UI where updates have occurred.
   • Automatically clear updates from cache once viewed.

Narrative

Imagine a user, Alex, who follows several content creators in the app. Alex receives a notification when a creator shares new content, complete with a clear CTA guiding him to this content. Simultaneously, Alex sees a visual update marker on the main interface, drawing his attention to the newly updated content space. This dual notification-update approach keeps Alex engaged and ensures he doesn't miss content from creators he cares about.

Success Metrics

1. Increase in user engagement metrics (e.g., daily active users, session length).
2. Higher click-through rates on notifications.
3. Positive user feedback on notification and update features.

Technical Considerations

1. Implement a new database model for storing notifications permanently.
2. Design cache mechanisms for temporary storage of updates.
3. Ensure scalability and responsiveness in notification and update systems.

Features Breakdown and Corresponding GitHub Tickets

Feature 1: Notification System Development

• Database Model and Backend Logic
  • Ticket #1: Design database schema for notifications.
  • Ticket #2: Implement backend logic for creating and updating notifications.
• Notification Display and User Interaction
  • Ticket #3: Design and implement the notification UI in the app
  • Ticket #4:: Develop Frontend Functionality for Notification CTAs and Post-Action Logic

Feature 2: Update System Development

• Cache Implementation and Backend Logic
  • Ticket #5: Develop cache system for temporary storage of updates.
  • Ticket #6: Implement backend logic for update creation and deletion.
• Update Display and User Interaction
  • Ticket #7: Design update markers in the UI.
  • Ticket #8: Develop frontend integration to display updates.