Skip to content

Notification with user activity tracking

name: Feature Request
about: Suggest a new feature or enhancement for the Corpus Collector Backend.
title: Notification with user activity tracking"
labels: "feature"
assignees: '@Bhaskar_Battula, @Pranav_rs, @saiteja3005 '

title: "feat(backend): implement user activity tracking and notification system"

🚀 Feature Request

Is your feature request related to a problem? Please describe.

Currently, there is no structured mechanism to track user activity or notify users about important interactions within the platform. Users are not informed when meaningful events occur, such as when another user connects with them or interacts with their content. This limits user engagement, reduces visibility into platform activity, and does not provide a modern, interactive experience similar to widely adopted social platforms. Additionally, there is no centralized user activity log that can be referenced for auditing or historical tracking.

Describe the solution you'd like

We need to implement a structured three-step feature to support user activity tracking and notifications:

Step 1 – Ensure Proper User Activity Logging
Create a dedicated user activity tracking system that records significant user actions (e.g., user interactions, content engagement, connection-related actions). This should include:

  • A database table for activity logs
  • Structured activity types (using enums)
  • Proper linkage between actor (initiator) and recipient (affected user)
  • Timestamps and metadata
  • Backend service-level integration so logs are created automatically during relevant actions

Step 2 – In-App Notifications
Introduce an in-app notification system that:

  • Generates notifications when relevant activity occurs
  • Associates notifications with recipient users
  • Exposes APIs to fetch notifications
  • Displays changes made on the users content, follow requests and responses

The in-app notification section should display meaningful interaction events and provide a user-friendly experience within the application interface.

Step 3 – Enable Push Notifications
After validating activity logging and in-app notifications:

  • Integrate push notification capability
  • Trigger push notifications for selected high-priority events
  • Ensure notification delivery only after backend validation
  • Maintain separation between activity logging, in-app notifications.

The overall system should be modular, scalable, and event-driven where possible.

Additional context

This feature should be implemented following clean architecture principles:

  • Backend-driven event generation
  • Dedicated activity log model
  • Dedicated notification model
  • Service-layer integration
  • Future-ready design for push notification support
  • Proper indexing and optimization for performance
Edited by POORNA CHANDRA SAI TEJA KUMPATLA