More project photos (2)
The problem
A Society Parking Slot Booking App for Android lets residents of a housing society see which parking slots are free on a live basement map, book one for a chosen date and time, and show a QR gate pass at the security gate, while the society admin watches occupancy, guest bookings and visitor fees. It replaces the paper register at the gate and the WhatsApp messages residents use to ask whether a slot is free, both of which depend on the guard remembering who parked where and cannot show availability in advance. The app keeps one shared slot record for the whole society, so a slot booked by one resident cannot be booked again, and every booking carries the flat number, vehicle number and time window the guard needs. The demo build covers a 48-slot society across 2 basement levels, with resident and guest booking types, EV charging bays and a 15-minute grace period.
| Option | Live availability | Advance booking | Guard verification | Visitor fee record |
|---|---|---|---|---|
| This app | Yes, live slot map | Yes, date + time slot | QR gate pass per booking | Yes, per-booking charges |
| Paper register / WhatsApp | No, ask the guard | No, first-come at the gate | Guard's memory | Manual, often missed |
| Generic city parking app | Yes, public lots only | Yes, public lots only | App payment receipt | City lots, not society slots |
Resident signs in with flat number and phone number.
Follow the working sequence
How it works
The Society Parking Slot Booking App for Android works as a single shared booking loop between residents, the security guard and the society admin. A resident signs in with flat number and phone number, opens the basement slot map, and sees the live state of all 48 slots across 2 basement levels. Tapping a free slot shows its size, rate and distance from the lift; the resident then picks a date, start time and duration, confirms in 4 taps, and the app writes one booking record to Cloud Firestore with the flat number, vehicle number and time window. The booking generates a QR gate pass sent to the resident on WhatsApp and appears on the guard's list. At the gate the guard scans the QR, checks the slot number and vehicle, and opens the boom barrier, while the admin dashboard updates occupancy, bookings and visitor fees in real time.
- The resident signs in with flat number and phone number through Firebase Authentication, and the app loads their flat, allotted slot and vehicle details from Cloud Firestore.
- The app reads the shared slot record and renders the live basement map — 48 slots across 2 basement levels — colour-coded as available, occupied, booked or EV charging.
- The resident taps a free slot, checks its size (2.5 m × 5.0 m for a car bay), rate and distance from the lift, then picks a date, start time and duration.
- On confirmation the app writes one booking record (slot, flat, vehicle, time window, booking type) to Cloud Firestore; the slot immediately shows as booked for every other resident.
- The app generates a booking ID and QR gate pass, sends the pass to the resident on WhatsApp, and adds the booking to the guard's verification list.
- At the gate the guard scans the QR, matches the slot number and vehicle number, and opens the boom barrier; a wrong slot or expired pass is refused.
- The admin dashboard updates occupancy, today's bookings and visitor fees in real time, and the slot returns to available automatically after the booking end time plus the 15-minute grace period.
Tech stack:
- Kotlin, Android Studio
- Firebase Authentication (phone + flat number)
- Cloud Firestore (slots, bookings, fees)
- Firebase Cloud Messaging (booking reminders)
- ZXing QR generation (gate pass)
- Material Design 3 (Android UI)
- WhatsApp share intent (gate pass delivery)
- CSV export (admin daily report)
| Parameter | Value |
|---|---|
| Platform | Android 8.0 (API level 26) and above |
| Language | Kotlin (Android Studio) |
| Demo society size | 48 slots (design target) |
| Basement levels | 2 levels, 24 slots per level (design target) |
| Car bay size | 2.5 m × 5.0 m (design target) |
| Booking flow | 4 taps from slot selection to confirmation (measured in the demo build) |
| Visitor rate | ₹20 per hour (design target, society-configurable) |
| Resident rate | ₹10 per hour after the free window (design target) |
| Resident free window | 2 hours per day (design target) |
| Grace period | 15 minutes after the booked end time (design target) |
| Backend | Cloud Firestore, one shared slot record |
| Gate pass | QR code, verified against booking ID |
| Admin export | CSV daily report |
| Demo data | 1 society, 32 bookings in the demo day, 3 waitlist requests |
Project features
The Society Parking Slot Booking App for Android is built around four capabilities that cover the whole parking problem for a housing society. First, a live slot map shows all 48 slots across 2 basement levels with colour-coded states — available, occupied, booked and EV charging — so a resident can see at a glance where space exists instead of driving down to check. Second, time-slot booking with a QR gate pass lets a resident pick a slot, date, start time and duration, and the booking generates a QR pass the security guard verifies before opening the boom barrier. Third, the society admin dashboard tracks occupancy by the hour, today's bookings, visitor fees collected and waitlist requests, and lets the admin block slots for maintenance or allot permanent slots to flats. Fourth, the app separates resident, guest and delivery bookings with different rules, including a free 2-hour daily window for residents and visitor charges for guests.
- [Live basement slot map] A colour-coded map of all 48 slots across 2 basement levels shows available, occupied, booked and EV charging bays, with level switching and a detail panel for the selected slot including size, rate and distance from the lift.
- [Time-slot booking with QR gate pass] A resident picks a slot, date, start time and duration, confirms in 4 taps, and receives a booking ID and QR gate pass that the security guard verifies before opening the boom barrier.
- [Resident, guest and delivery booking types] Resident bookings get a free 2-hour daily window, guest bookings are charged at the society visitor rate, and delivery bookings are short-window entries, each with its own rules and cancellation window.
- [Society admin dashboard] The admin sees occupancy by the hour, today's booking list with flat and vehicle numbers, visitor fees collected and waitlist requests, and can export the day's report as a CSV file.
- [Slot allotment and blocking] The admin can allot a permanent slot to a flat and block a slot for maintenance, so allotted and blocked slots never appear as bookable on the resident map.
- [Booking management and extension] Residents can extend a booking before its end time when the next hour is free, cancel free of charge before the cut-off, and rely on a 15-minute grace period after the booked end time.
- [Firebase Authentication and Cloud Firestore] Residents sign in with their flat number and phone number, and all slots, bookings and fees live in one shared Cloud Firestore record, so a slot booked by one resident cannot be double-booked by another.
What is included
- Complete Kotlin Android app source code (resident booking, QR gate pass, admin dashboard)
- Firebase backend setup: Authentication, Cloud Firestore structure and security rules
- Working demo app with a 48-slot demo society (2 basement levels, EV bays, guest and delivery bookings)
- Project report PDF (background, system design, database structure, methodology, results)
- PPT presentation for final review
- Viva Q&A preparation document (Android lifecycle, Firebase, Firestore rules, QR verification)
- Setup guide: building the APK, configuring Firebase for your society, and demo instructions
- To request a quotation on WhatsApp, share your society size (number of slots and levels), whether you need guest billing and UPI payment, and your delivery deadline — the quotation will confirm scope, price and delivery date before work starts.
Limitations & prerequisites
- The demo society is a 48-slot, 2-level layout; a larger society needs its slot data reconfigured, which is a setup step, not a code change.
- Visitor and guest rates (₹20 per hour visitor, ₹10 per hour resident after the free window) are design targets set for the demo society — your society's actual rates are configured during setup.
- The QR gate pass is verified against the booking record in the app; it does not integrate with an automatic number-plate camera or a boom barrier motor, which would be separate hardware work.
- UPI or online payment for visitor fees is not part of the base build — fees are recorded in the app and collected by the society; payment integration can be added on request.
- The app needs internet connectivity to read and write bookings; without a connection the slot map shows the last synced state and new bookings cannot be confirmed.
- Real-time slot occupancy depends on residents and the guard keeping bookings accurate — the app does not sense vehicles, so a car parked without a booking is invisible to the map.
- The demo data (32 bookings, visitor fees of ₹1,240 for the demo day) belongs to the demo society and is not a measurement of any real society's usage.
Frequently Asked Questions
How does the slot booking actually work for a resident?
A resident signs in with flat number and phone number, opens the live basement map of all 48 slots, taps a free slot, picks a date, start time and duration, and confirms in 4 taps. The app writes one booking record to Cloud Firestore, generates a booking ID and QR gate pass, and sends the pass on WhatsApp. At the gate the guard scans the QR and checks the slot and vehicle before opening the barrier.
How does the society admin use the app?
The admin dashboard shows occupancy by the hour, today's booking list with flat and vehicle numbers, visitor fees collected and waitlist requests. From the same screen the admin can allot a permanent slot to a flat, block a slot for maintenance, approve guest bookings and export the day's report as a CSV file for the society accounts.
Can two residents book the same slot at the same time?
No. All slots, bookings and fees live in one shared Cloud Firestore record, and the booking is written as a single transaction: the moment one resident confirms, the slot shows as booked for everyone else and any second tap on the same slot is refused. If two residents tap the same free slot at once, only the first confirmed booking succeeds and the second resident sees the slot as booked.
Does it work without internet?
Not for new bookings. Reading live availability and confirming a booking both need a connection to Cloud Firestore, so without one the app shows only the last synced slot map and blocks new bookings until the connection returns, and a booking made offline would risk double-booking the same slot. The QR gate pass already issued stays valid for the guard to verify, since the guard's list was synced when the booking was made.
Can it be customized for my society?
Yes — slot count, basement levels, bay sizes, resident free window, visitor and guest rates, and the society name are all configuration, not code changes. UPI payment for visitor fees, a guard verification app, society notice-board integration and multi-society support can be added on request, with scope, price and delivery date confirmed in the WhatsApp quotation first.
Is this project suitable for a final-year project?
Yes — for Computer Engineering, IT and Mobile Application Development programs. It demonstrates Android app development in Kotlin, Firebase Authentication and Cloud Firestore, QR-based verification, role-based resident and admin flows, and a real society-management problem with a working demo that can be tested with actual residents.
Components & software requirements
- Kotlin, Android Studio
- Firebase Authentication (phone + flat number)
- Cloud Firestore (slots, bookings, fees)
- Firebase Cloud Messaging (booking reminders)
- ZXing QR generation (gate pass)
- Material Design 3 (Android UI)
- WhatsApp share intent (gate pass delivery)
- CSV export (admin daily report)
Delivery information
Built-to-order project. Delivery timeline is shared after order confirmation based on current queue.
Support terms
Complete documentation, setup guide, and viva preparation included. Support for setup and explanation provided.
Download free synopsis (PDF)
Enter your name and WhatsApp number — the synopsis PDF downloads immediately. We may send occasional project updates on WhatsApp; no spam.