How insanecoder789/offlineqr-attendance works
OfflineQR is an institution-focused, offline-first attendance system. Faculty open classroom sessions and present rotating signed QR codes; students scan in the registered app, retain signed proofs locally, and synchronize them when reachable. The backend verifies proofs and updates attendance records for faculty review. The README documents these product capabilities, identity and device governance, and a separate public editorial site with proposal-PDF generation. Source excerpts show backend routing and attendance verification; mobile internals and most portal implementations were not sampled, so those links reflect README-documented behavior.
Main entry points: main.py FastAPI routes · FacultyPortalShell.tsx Faculty workspace · attendance_service.py Signed QR session · MainActivity.kt Student app
Components 19
Classroom attendance
- Faculty workspace
faculty-portal/src/components/FacultyPortalShell.tsx - Session operations
backend/app/attendance_service.py - Signed QR session
backend/app/attendance_service.py - Student app
client/android/app/src/main/kotlin/com/offlineqr/attendance/MainActivity.kt - Local proof outbox
client/android - Proof verification
backend/app/attendance_service.py - Attendance records
backend/app/attendance_service.py
Identity and governance
- Identity and sign-in
backend/app/faculty_identity_service.py - Device governance
backend/app/device_service.py
Backend services
- FastAPI routes
backend/app/main.py - PostgreSQL
backend/app/db.py - Redis coordination
backend/app/redis_service.py
Web surfaces
- Portal API client
faculty-portal/src/api.ts - Admin API client
faculty-portal/src/admin-api.ts - Editorial website
faculty-portal/src/components/marketing/PublicPage.tsx - Proposal PDF endpoint
faculty-portal/src/lib/commercial/proposal-pdf.ts
Other components
- Faculty
- Student
- ICT administrator
Connections 21
- Faculty → Faculty workspace: operates
README.md - Faculty workspace → FastAPI routes: uses
README.md - Faculty workspace → Session operations: starts sessions
README.md - Session operations → Signed QR session: issues challenge
README.md - Faculty workspace → Signed QR session: displays QR
README.md - Student → Student app: uses
README.md - Signed QR session → Student app: is scanned by
README.md - Student app → Local proof outbox: stores proofs
README.md - Local proof outbox → FastAPI routes: syncs proofs
README.md - FastAPI routes → Proof verification: routes proofs
backend/app/main.py - Proof verification → Attendance records: records results
backend/app/attendance_service.py - FastAPI routes → Faculty workspace: publishes roster updates
README.md - FastAPI routes → PostgreSQL: reads and writes
backend/app/db.py - FastAPI routes → Redis coordination: coordinates sessions
backend/app/redis_service.py - Faculty workspace → Portal API client: requests workspace data
- Portal API client → FastAPI routes: calls
- ICT administrator → Admin API client: governs devices
README.md - Admin API client → FastAPI routes: calls
- FastAPI routes → Identity and sign-in: authenticates faculty
backend/app/main.py - FastAPI routes → Device governance: routes device actions
backend/app/main.py - Editorial website → Proposal PDF endpoint: submits proposal
README.md