A lightweight, fast, research-focused attendance application for academic institutions enabling real-time marking, timetable management, and comprehensive analytics.
- MASTER_README.md — Project overview, architecture, vision, 5-phase timeline
- COMPLETE_DEVELOPER_DOCUMENTATION.md — Technical deep-dive, setup, API reference
- backend/README_DEV.md — Backend development quick start
- mobile/README.md — Mobile (Flutter) development setup
- docs/ARCHITECTURE.md — System design & data flow
- docs/API.md — Complete API reference (25 endpoints)
Node.js 18+, npm 9+, Docker, Flutter 3.x, PostgreSQL 14+# 1. Clone repo
git clone <url>
cd attendance-app
# 2. Start PostgreSQL + Redis
docker-compose up -d
# 3. Backend setup
cd backend
npm install
npm run db:migrate
npm start
# ✓ Server on http://localhost:3000
# ✓ Health check: curl http://localhost:3000/api/v1/healthcd mobile
flutter pub get
flutter runattendance-app/
├── backend/ # Node.js + Express API
│ ├── src/
│ ├── tests/
│ ├── docker-compose.yml
│ └── README_DEV.md
├── mobile/ # Flutter iOS + Android
│ ├── lib/
│ ├── test/
│ └── pubspec.yaml
├── docs/ # Documentation
│ ├── ARCHITECTURE.md
│ ├── API.md
│ ├── DEPLOYMENT.md
│ ├── SECURITY.md
│ ├── TROUBLESHOOTING.md
│ └── ADR/ # Architecture Decision Records
├── .gitignore
├── LICENSE
├── MASTER_README.md # Full spec
└── COMPLETE_DEVELOPER_DOCUMENTATION.md
| Aspect | Details |
|---|---|
| Build Time | 6 weeks (5 FTE) |
| Target Users | Faculty, HoD, Admin, Students (future) |
| Marking Speed | <2 minutes for 60 students |
| App Size | <40 MB APK, <20 MB installed |
| Memory | <150 MB peak |
| Uptime | 99.9% (SLA) |
| Real-time | <2 sec HoD dashboard update |
| Tech Stack | Flutter, Node.js, PostgreSQL, Redis, AWS |
Problem: Faculty spend 10–15 minutes manually marking attendance with no real-time visibility, no analytics, no audit trail.
Solution: One-tap app that marks 60 students in <2 minutes. Real-time HoD dashboard. Rich analytics. Immutable audit log.
Impact: 7x faster, zero errors, real-time visibility, rich insights, full compliance.
| Phase | Weeks | Focus |
|---|---|---|
| 0 | 1–2 | Foundation (DB, Auth, Express scaffold) |
| 1 | 3–4 | Core Attendance Marking |
| 2 | 5–6 | Timetable & Tentative Lectures |
| 3 | 7–9 | Analytics & HoD Dashboard |
| 4 | 10–11 | Security & Lite Optimization |
| 5 | 12–14 | Deployment & Beta Testing |
| Document | Purpose |
|---|---|
| MASTER_README.md | Project overview, vision, architecture, timeline, budget |
| COMPLETE_DEVELOPER_DOCUMENTATION.md | Technical setup, database, API, testing, deployment |
| docs/ARCHITECTURE.md | System design, data flow, component responsibility |
| docs/API.md | OpenAPI spec, all 25 endpoints with examples |
| docs/DEPLOYMENT.md | AWS setup, monitoring, scaling, incident response |
| docs/SECURITY.md | OWASP checklist, auth flows, encryption |
| docs/CONTRIBUTING.md | Code style, PR process, commit conventions |
| docs/TROUBLESHOOTING.md | Common issues, debug steps, solutions |
| backend/README_DEV.md | Backend setup & development |
- Clone the repo
- Create a feature branch (
git checkout -b feature/your-feature) - Make changes
- Commit with conventional messages (
feat:,fix:,docs:) - Push and create PR
- Code review required before merge
- Tests must pass (>70% coverage)
See CONTRIBUTING.md for details.
Questions? Check:
- TROUBLESHOOTING.md — Common issues
- docs/API.md — Endpoint details
- docs/DEPLOYMENT.md — Infrastructure
- GitHub Issues — Report bugs or feature requests
Status: Phase 0 (Foundation) — In Development
Timeline: 6 weeks (started 2026-04-10)
Confidence Level: Very High ✅✅✅