More project photos (3)
The problem
Finding a badminton partner is harder than finding a court. Players post in locality WhatsApp groups, skill levels mismatch, and half the group drops out by evening. Separately, court booking is a phone call to the venue. This project solves both together. The partner finder shows nearby players with skill badges, playing schedules and a match percentage computed from level, distance and availability overlap; players can invite each other or join open games that list how many spots are left. The booking side is a live slot grid — courts as rows, time slots as columns — with booked slots struck through, peak/off-peak rates, and one-click confirmation generating a booking reference. Booking with an invited partner links the two halves: reserve the court and your partner gets the invite. It is built on plain PHP/MySQL with honest, explainable matching (weighted scoring, not "AI").
Creates a profile, finds partners and books courts.
Follow the working sequence
How it works
- Players create a profile: skill level (beginner/intermediate/advanced), locality, usual playing times and singles/doubles preference.
- The finder computes match scores against nearby players from level proximity, distance and schedule overlap, and ranks the cards.
- Players invite matches directly, or join an open game from the board (spots decrement as players join).
- For the court, the player picks a venue and date; the slot grid renders from the bookings table with peak/off-peak rates.
- Selecting an available slot shows the summary; confirming writes the booking and issues a reference code.
- The booking appears under My Bookings for both players; cancellations free the slot back to the grid.
Tech stack:
- PHP 8 (backend)
- MySQL (players, venues, courts, slots, bookings, invites, ratings)
- HTML5, CSS3, JavaScript (front end, slot grid)
- Session-based auth
| Parameter | Value |
|---|---|
| Architecture | PHP + MySQL, session auth |
| Match score | Weighted: skill proximity, distance, schedule overlap (documented weights) |
| Slot granularity | 1-hour slots, 6 AM – 10 PM per venue (configurable) |
| Pricing | Peak/off-peak rates per venue, configurable |
| Cancellation | Free up to 4 hours before start (configurable) |
| Database tables | Approximately 8 (users, players, venues, courts, bookings, invites, games, ratings) |
| Deployment | LAMP / shared hosting; mobile-responsive |
Project features
- [Partner matching] Player cards with skill level, locality, schedule and game preference, ranked by a transparent match score (level + distance + availability).
- [Open games board] Games looking for players show venue, level, and spots remaining; one click joins.
- [Live court slot grid] Courts × time slots with real-time booked/available states, peak vs off-peak pricing per slot.
- [Booking flow] Select a slot, see court/date/rate summary, confirm to get a booking reference; free cancellation up to 4 hours before.
- [Invitations] Invite a matched partner to a booked slot; the booking shows who is coming.
- [Player profiles & ratings] Post-game star ratings build a reliability record per player.
- [My bookings] Upcoming bookings with cancel option, plus past games history.
What is included
- Complete platform source (finder, games board, booking, profiles)
- MySQL schema with sample players, venues and bookings
- Match-scoring module with documented weights
- Project report PDF (requirements, matching design, ER diagram, screenshots, testing)
- PPT presentation for final review
- Viva Q&A preparation document (matching algorithms, booking concurrency, roles)
Limitations & prerequisites
- Match percentages come from a documented weighted score, not machine learning — the project makes no AI claim.
- Distances use the locality the player enters; there is no live GPS tracking in the base build.
- Payments in the base build are pay-at-venue; online payment integration is future scope.
- Skill levels are self-declared with post-game ratings as the check; there is no formal assessment.
- The base build covers one city; multi-city support needs a locality hierarchy extension.
Frequently Asked Questions
How is the match percentage computed?
A weighted score: skill-level proximity (40%), distance (30%) and playing-time overlap (30%). The weights and bands are documented in the report — fully explainable in a viva.
What stops double-booking a court slot?
The booking insert runs in a database transaction with a uniqueness constraint on (court, date, slot); concurrent clicks resolve to exactly one winner.
Can venues set their own prices?
Yes — peak/off-peak rates and peak hours are per-venue configuration, editable without code changes.
How do open games work?
A player creates a game (venue, time, level, spots); others join until spots fill. The creator can see who joined and message them.
Is there a mobile app?
The base build is a mobile-responsive web app, which covers the use case; a native app is listed as future scope.
Is this project suitable for a final-year project?
Yes — for Computer Science, IT and Web Development programs. It demonstrates matchmaking logic, reservation concurrency, two-sided workflows and community features. Suitable for B.E./B.Tech final-year projects in Computer Science, IT and Web Development.
Components & software requirements
- PHP 8 (backend)
- MySQL (players, venues, courts, slots, bookings, invites, ratings)
- HTML5, CSS3, JavaScript (front end, slot grid)
- Session-based auth
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.