Housing Society Visitor Management Android App

The paper visitor register at a society gate is slow, illegible and useless in an emergency — nobody can answer "who is inside right now?" from a smudged notebook. Guards juggle phone calls to flat owners for every guest, delivery riders wait at the gate, and managing committees have no data on footfall or repeat offenders. This project builds GatePass, an Android app with two faces: a guard app for fast check-ins and a resident app for approvals and passes. A visitor is logged with name, phone, purpose and flat; the owner gets a push request and approves or denies in one tap. Residents pre-generate QR gate passes for expected guests, domestic help and cabs — the guard scans instead of calling. Every event is timestamped into a queryable entry-exit log with filters by date, flat, purpose and status, and the committee dashboard shows live occupancy and daily summaries. An offline write queue keeps the gate operational through network drops, syncing when connectivity returns.

1. The guard opens the app, selects the visit purpose and flat, and enters the visitor's name and phone — or scans the visitor's QR pass to pre-fill everything.
2. If the flat has approval enabled, an FCM push request goes to the resident with the visitor's details; approve/deny writes back to the entry record.
3. On approval (or for pass-holders), the guard confirms entry; the event is timestamped into the log with the guard's ID.
4. At exit, the guard taps the active entry to stamp the exit time; the resident can also be notified.
5. Residents generate QR passes from the resident app: guest name, vehicle number, validity window — encoded as a signed token the guard app verifies offline.
6. All events sync to Firestore; the committee dashboard aggregates live occupancy and exports daily CSV reports.
7. Without connectivity, entries queue in Room with device timestamps and sync later, flagged as backfilled.

Tech stack:

• Kotlin, Android SDK with Jetpack (CameraX, Room, Navigation)
• Material 3 design components
• ZXing (QR generation and scanning)
• Firebase Authentication (guard/resident roles)
• Cloud Firestore (visitors, passes, approvals)
• Firebase Cloud Messaging (approval requests)
• Room (offline entry queue)

• [Guard check-in flow] Log a visitor in under 15 seconds: name, phone, purpose, flat, photo capture — with recent-visitor autocomplete for repeat entries.
• [QR gate passes] Residents generate time-bound QR passes for guests, cabs and deliveries; the guard scans to auto-fill the entry.
• [Instant resident approvals] The flat owner receives a push approval request with visitor details and approves or denies in one tap.
• [Entry-exit log] Every gate event timestamped and searchable by date, flat, purpose, visitor name and status — the paper register, queryable.
• [Pre-approved regulars] Domestic help, drivers and staff get recurring passes so daily entries don't need fresh approvals.
• [Committee dashboard] Live "who is inside" count, daily footfall summaries and per-flat visitor history for the managing committee.
• [Offline queue] Entries captured without connectivity are queued in Room and synced to Firestore on reconnect, marked with capture time.

• Complete Kotlin Android source code (guard + resident apps, single project)
• Firestore data model, role-based security rules and indexes
• Debug APK for testing on a real device
• Seed dataset: flats, residents, visitors, sample passes
• Project report PDF (problem analysis, workflow design, schema, screens, testing)
• PPT presentation for final review
• Viva Q&A preparation document (QR tokens, offline sync, FCM, Firestore rules)
• Build and Firebase setup guide