College Fest Volunteer Management Android App with Shift Scheduling

College fests run on volunteers, and most organizing committees still manage them on WhatsApp groups and shared spreadsheets. Shift lists get buried under chat messages, last-minute dropouts go unnoticed until a desk stands empty, and nobody can say with certainty who actually showed up for their slot. The result is familiar to anyone who has volunteered: an overstaffed registration desk next to an unmanned entry gate, with coordinators firefighting instead of running the fest.

This project builds FestCrew, a native Android app that replaces that chaos with a single live roster. A coordinator creates shifts for each fest team — stage, registration, hospitality, security — assigns volunteers from the pool, and publishes the roster when final. Volunteers see only their own shifts, request swaps when clashes arise, and get push notifications when a roster changes. At the venue, each shift produces a rotating QR check-in code the coordinator verifies at the desk, so attendance is recorded instead of assumed. Built in Kotlin with Jetpack Compose on Firebase, the app caches the roster offline, because fest venues rarely have reliable Wi-Fi.

1. The coordinator signs in and onboards the volunteer pool; each volunteer gets a Firebase Auth account tagged with a fest team (stage, registration, hospitality, security).
2. The coordinator creates shifts — title, team, date, time, venue and slots needed — and assigns volunteers from the pool; shifts remain drafts until the roster is final.
3. Publishing a shift writes it to Firestore and triggers an FCM push to every assigned volunteer, who then sees it under "My shifts" — available offline from the cache.
4. A volunteer who cannot make a slot sends a swap request with a reason; the coordinator approves or rejects it, and the roster plus both notification feeds update.
5. At the venue, the volunteer opens the shift and shows the rotating QR check-in code; the coordinator verifies it at the desk and marks attendance against the live roster.
6. Coordinators track coverage from the roster dashboard — published vs draft shifts, assigned headcount per slot, and check-in counts for every shift.

Tech stack:

• Kotlin
• Jetpack Compose (Material 3)
• Firebase Authentication
• Cloud Firestore (offline persistence)
• Firebase Cloud Messaging
• ZXing QR code library
• Android Studio
• Git

• [Role-based login] Coordinator and Volunteer roles sign in through Firebase Authentication; each role opens its own home screen and permissions, so volunteers never see roster-management controls.
• [Shift creation] The coordinator defines shifts with title, team, date, start/end time, venue and required headcount; new shifts stay as drafts until the roster is final and published.
• [Volunteer assignment] The coordinator picks volunteers from the registered pool into each shift's slots; assignments write to Firestore and appear on the volunteer's phone immediately.
• [QR check-in at the venue desk] Every shift generates a rotating check-in code rendered as a QR; the coordinator verifies it against the live roster at the desk, recording attendance with a timestamp.
• [Swap-request approval flow] A volunteer requests a swap with a written reason; the coordinator approves or rejects it, the roster updates, and both sides are notified of the decision.
• [Offline shift list] Firestore offline persistence caches the roster, so volunteers can view their shifts in venues with no connectivity; publishing and check-in need internet and are disabled offline.
• [Push notifications] FCM alerts for roster publication, new assignments and swap decisions, so no volunteer misses a change to their schedule.

• Complete Kotlin + Jetpack Compose source code
• Firestore data model and security rules
• Debug APK for demo and viva presentation
• Setup guide (Firebase project setup, build steps)
• Project report PDF (architecture, Firestore schema, QR flow, testing notes)
• PPT presentation for final review
• Viva Q&A preparation document (Firebase, Compose, offline caching, FCM, QR)
• Demo data seeder (teams, volunteers, sample shifts)