How zashouri91/feedbackpulse works
Main System Components
a) Frontend Layer:
• React-based SPA structure (indicated by src/App.tsx and Vite configuration)
• Feature modules:
• Survey Management
• Analytics Dashboard
• User Management
• Authentication
• Notifications
b) API/Backend Layer:
• Supabase Integration:
• Real-time capabilities (indicated by realtime.sql migration)
• Authentication services
• Database access
c) Database Layer:
• Supabase PostgreSQL database with the following main entities:
• Surveys
• Templates
• Responses
• Users
• Groups
• Locations
• Audit Logs
• Notifications
Component Relationships
a) Client-Side Flow:
UI Components → Hooks → API Clients → Supabase Client
b) Data Flow:
Frontend ←→ Supabase Real-time ←→ Database
Specific Architectural Elements
Key architectural patterns:
a) Authentication Flow:
• Auth provider component integration
• RBAC implementation (role-gate and permission-gate components)
b) Real-time Updates:
• Websocket connections for live feedback
• Notification system architecture
c) Analytics Pipeline:
• Data collection flow
• Analytics processing
• Dashboard visualization
Technical Stack Indicators
• React + TypeScript (Frontend)
• Supabase (Backend + Database)
• Tailwind CSS (Styling)
• Cypress (Testing)
• Sentry (Error Tracking)
• PostHog (Analytics)
Important Details
a) Security Layer:
• RLS policies (shown in migrations)
• Authentication boundaries
• Permission checks
b) Feature Modules:
• Survey management
• Template system
• Analytics dashboard
• User management
• Audit logging
• Notification system
┌─────────────────────────────────────────────┐
• Client Layer │
• (React Components, Hooks, Context Providers)│
• ┤
• Integration Layer │
• (API Clients, Real-time Subscribers) │
• ┤
• Supabase Layer │
• (Auth, Storage, Real-time, RLS Policies) │
• ┤
• Database Layer │
• (PostgreSQL Tables, Functions, Triggers) │
• ┘