college-attendance

bysukuna king

Build a production-ready **College Attendance Management Web App** for a Class Representative managing 70–100+ students. Use **React + TypeScript + Tailwind/shadcn**, **Node.js + Express**, **PostgreSQL + Prisma**, JWT authentication, and real database persistence. ### Core Features * CR and Student login with role-based access. * Dashboard showing total students, present, absent, attendance %, trends, and low-attendance alerts. * Mobile-first **Take Attendance** screen with USN, roll number, name, Present/Absent/Leave controls. * Mark all present, bulk actions, undo, filters, and edit previous attendance. * **Voice attendance:** CR can say roll numbers, USNs, or student names and instantly mark attendance. Support commands like present, absent, leave, undo, clear, save, and mark-all-present. * Use confidence-based matching and **never mark an uncertain student automatically**; show a “Did you mean?” option. * Voice and manual attendance must use the same validation/state system. * Student profiles with overall %, subject-wise attendance, and attendance history. * Subject and timetable management. * Reports and analytics with CSV, Excel, and PDF export. * Excel/CSV student import with validation and preview. * Audit log for every attendance edit. * Optional QR attendance. * Light/dark mode and accessible responsive UI. * All attendance percentages must be calculated from the database and update immediately after changes. * Secure authentication, validation, rate limiting, transactions, and offline-safe attendance state. ### Voice Requirements Use Web Speech API with optional Whisper/Vosk fallback. Support `en-IN`, continuous listening, push-to-talk/wake-word modes, microphone testing, confidence thresholds, and voice confirmations. Prevent duplicate or incorrect markings. ### Deliverables Provide the complete working frontend, backend, database schema/migrations, seed data for ~85 students, demo credentials, Docker setup, tests, README, and no placeholder/TODO functionality. The final application must be **fully functional, fast, mobile-friendly, reliable, and production-quality**, not a mockup or static prototype.