Skip to content

Feature Request: Add Back & Improve Features

name: Feature Request
about: Suggest an idea for BharatVerse
title: '[FEATURE] Lite Reintroduction & Community Improvements'
labels: enhancement
assignees: ''

Feature Summary

Reintroduce some previously removed features in a lighter form and enhance community collaboration tools. This keeps BharatVerse simple, fast, and user-focused, while preparing for future expansion.

Problem Statement

Currently, the app feels too minimal. Some useful cultural and collaboration features (audio, visual heritage, admin roles, performance stats) are missing, which limits engagement and growth. Users need more ways to interact, share, and manage contributions.

Proposed Solution

  • Reintroduce Audio Module (Lite): simple record + playback, no heavy AI.
  • Re-enable Visual Heritage: image uploads with backend prep for feed.
  • Add Admin Roles: basic moderation and permissions.
  • Create Performance Dashboard (Lite): simple stats (stories posted, active users, GitLab contributions).
  • Expand Community Hub: tagging/mentions, notifications for replies & collaboration invites.

Alternative Solutions

  • Keep app minimal and delay these until future versions (risk: user engagement drops).
  • Integrate third-party tools for collaboration and analytics (risk: fragmented user experience).

Use Cases

  • Use case 1: A community moderator can manage posts without needing advanced admin tools.
  • Use case 2: A user uploads a cultural image to preserve heritage.
  • Use case 3: A contributor tracks their GitLab roles and cultural stories shared in a single dashboard.
  • Use case 4: Community members get notified when tagged or invited to collaborate.

Cultural Context

  • Helps preserve cultural stories not just in text, but also through images and basic audio.
  • Strengthens community collaboration around cultural preservation.

Technical Considerations

  • Audio and visual modules should be lightweight.
  • Basic role management needs to be added without complex RBAC.
  • Dashboard should use existing metrics to avoid heavy computation.
  • Minimal performance impact to keep app fast.

Additional Context

This is a phased approach:

  1. Community hub expansion + lite performance dashboard.
  2. Visual heritage + audio lite.
  3. Basic admin roles.

Priority

  • Low
  • Medium
  • High
  • Critical