HMS (Hostel Management System)
Real-world deployed system with 53 active daily users
✦ Key Highlights
- In daily active production use by 53 users
- Serves 50 students, 1 warden, and 2 kitchen staff
- Full-stack: NestJS/Prisma/Postgres backend + React Native mobile app
- Real deployed system, not a portfolio demo
Overview
A full-stack hostel management system in daily active production use by 50 students, 1 warden, and 2 kitchen staff. Built with NestJS, Prisma, and PostgreSQL on the backend, with a React Native mobile frontend. A real deployed system, not a demo.
Documentation
Hostel Management System (HMS) — MVP
Native mobile app (Android + iOS) + REST API for hostel operations. Fast MVP: meal-ready push, meal attendance, complaints, notices, auth.
Full product design: HOSTEL_MANAGEMENT_SYSTEM_DESIGN.md.
``
MHM/
├── backend/ NestJS + Prisma + PostgreSQL (API)
└── mobile/ React Native + Expo (Android + iOS app)
Prerequisites
1. Backend
`bash`
cd backend
cp .env.example .env # then edit DATABASE_URL + JWT secrets
npm install
npm run prisma:generate
npm run prisma:migrate # creates tables (name it e.g. "init")
npm run db:seed # seeds 1 hostel, warden, 3 students, categories
npm run start:dev # http://localhost:3000/api/v1
Seeded logins (password Password123!):warden@hostel.test
Smoke test:
`bash`
curl -X POST http://localhost:3000/api/v1/auth/login \
-H "Content-Type: application/json" \
-d '{"email":"warden@hostel.test","password":"Password123!"}'
2. Mobile app
`bash`
cd mobile
npm install
npm start # scan QR with Expo Go, or press a/i for sim
API URL config: mobile/app.json → extra.apiUrl.localhost works.10.0.2.2.apiUrl to your PC LAN IP, e.g. http://192.168.1.5:3000/api/v1. Phone + PC same Wi-Fi.
Demo flow
1. Login warden on one device/sim → tap 🍛 Lunch → push fan-out fires.
2. Login student on second device → gets alert, marks meal, sees monthly %.
3. Student files complaint → warden sees it, advances status → resolved.
4. Warden posts notice → students notified + appears in Notices tab.
> Push needs physical device (simulators skip token). Without it, meal-ready still logs server-side + updates in-app — flow testable end-to-end.
What's in / out (v1)
In: auth (JWT + refresh + reset), RBAC (warden/student), meal-ready push, notifications inbox + history, meal attendance + stats, complaints (photo URLs, triage, replies), notices, dashboards.
Out (deferred, schema-ready): fees/payments, leave, rooms/beds, visitors/QR, maintenance, inventory, feedback analytics, SOS, reports/PDF, web dashboard, multi-hostel admin. See design doc §0.5.
Tech
Backend: NestJS 10, Prisma 5, PostgreSQL, Passport-JWT, argon2, expo-server-sdk (push), helmet.
Mobile: Expo 51, Expo Router, TanStack Query, Zustand, axios, expo-secure-store, expo-notifications.