GameSlot: Turf Booking & Management Platform — hero banner
    Back to Projects
    Sports Tech
    SDG 3
    SDG 11

    GameSlot: Turf Booking & Management Platform

    A seamless turf discovery, booking, and management platform — Sign Up, Book, Play. Find nearby courts, schedule games, and manage bookings effortlessly.

    My Role
    Lead Product Designer
    Deployment
    5+ Turfs Listed

    Overview

    GameSlot is a comprehensive sports turf booking and management platform that connects players with nearby courts and sports complexes. The app enables users to search for turfs, view availability, book time slots, and manage their bookings — all from a single intuitive interface. With features like real-time court availability, QR-based check-in, and smart scheduling, GameSlot simplifies the entire sports facility booking experience for both players and venue operators.

    The Problem

    Urban sports — football, cricket, padel, badminton — have grown explosively across South and Southeast Asia, but the booking experience has not kept up. Most venues are still scheduled by WhatsApp, Facebook Messenger, or a paper diary at the gate. Double-bookings, lost deposits, and arguments over who-booked-which-slot are routine weekend friction.

    For players, there is no canonical way to find a nearby court at a given hour on a given day. They rely on word-of-mouth, past visits, or running a phone tree through their friend group. For venue operators, there is no canonical way to publish their real inventory; they end up managing three or four fragmented communication channels and still miss bookings.

    GameSlot was designed as a two-sided product with opposing constraints: players want booking to feel like ordering a ride — three taps, done — while venue operators need granular control over pricing, availability, and cancellation rules. Reconciling those two worldviews drove nearly every UX decision in the product.

    App Showcase

    GameSlot App Overview
    Sign Up. Book. Play — All in one app
    Search Courts
    Search & find nearby turfs and courts
    Book Court
    Book your preferred time slot instantly
    Manage Bookings
    Effortlessly manage your upcoming schedule

    Core Features

    1. 01

      Search & discover nearby turfs and sports complexes with distance and ratings

    2. 02

      Real-time court availability with date and time slot selection

    3. 03

      Multi-sport support — Padel Tennis, Football, Cricket, and more

    4. 04

      Booking management with upcoming, pending, and completed status tracking

    5. 05

      QR code-based check-in for seamless venue access

    6. 06

      User profiles with booking history and loyalty levels

    Architecture Decisions

    Three-tap booking flow

    Search, Select, Confirm. Everything else was cut. The decision budget for a player who wants to book a 9pm game on a Thursday evening is vanishingly small; any extra screen is a drop-off. We resisted the temptation to add filters, loyalty upsells, friend invites, or review prompts inside the critical booking path. They live elsewhere in the product — optional, never blocking.

    Real-time slot locking with soft holds

    A slot is soft-locked the moment a player selects it and hard-locked after payment authorization. If payment fails or the player abandons, the soft lock releases in 90 seconds. This single mechanic eliminated the double-booking class of support ticket — the dominant complaint category in the pre-GameSlot booking workflow — without needing distributed transactions or any exotic infrastructure.

    Flexible cancellation policy engine

    Venues have strong opinions about cancellation. Some refund in full up to 24 hours before the slot; some offer store credit only; some are brutal — no refunds, period. We built the policy as a venue-configurable rule set rather than hard-coding one answer, and surfaced the active rule inline at the point of booking so the player knows exactly what they're agreeing to before they pay.

    QR-based contactless check-in

    Check-in was the easy-to-miss step. A booking code printed on a confirmation screen is fine until three players arrive at a venue entrance simultaneously and the gate staff fumbles through three separate phones. A single-scan QR with server-side validation — and an obvious success state on the gate-side tablet — took that friction out entirely and materially improved operator feedback.

    Tech Stack

    • React Native
    • Node.js
    • PostgreSQL
    • REST API
    • Google Maps API
    • Push Notifications
    • QR Code
    • Payment Gateway

    Challenges & Solutions

    Challenge

    Handling real-time slot availability across multiple venues simultaneously

    Solution

    Implemented real-time slot locking mechanism to prevent double bookings

    Challenge

    Building an intuitive booking flow that minimizes drop-offs

    Solution

    Designed a 3-step booking flow — Search, Select, Confirm — with minimal friction

    Challenge

    Managing cancellations and rescheduling without double-booking

    Solution

    Built an automated cancellation policy engine with refund management

    Challenge

    Integrating diverse payment methods for different regions

    Solution

    Integrated multiple payment gateways with unified checkout experience

    Challenge

    Ensuring accurate location-based search with distance calculations

    Solution

    Used Google Maps API with optimized geospatial queries for accurate distance results

    Results & Impact

    • 5+ turf venues onboarded

    • Streamlined 3-step booking process

    • Real-time availability across all venues

    • QR-based contactless check-in

    • Multi-sport support with flexible scheduling

    Lessons Learned

    1. 01

      Two-sided marketplaces live and die by operator experience first, not player experience. The player gets the polish if the venue operator trusts the system enough to publish their real inventory on it.

    2. 02

      Soft-hold expiry windows are a UX choice, not just an infrastructure choice. Too short (30s) and we lost legitimate bookings mid-payment; too long (3min) and we starved a concurrent player out of the same slot. 90 seconds turned out to be the sweet spot.

    3. 03

      Distance-sorted search is almost never the correct default. Sorting by 'available right now at a fair price' out-performs sorting by raw geographic proximity, because players are time-box-driven first and distance-driven second.

    4. 04

      Payment UX is product UX. A single failed payment gateway call is enough to lose the player for the weekend. Integrating redundancy across gateways was the single highest-ROI engineering investment post-launch.

    Interested in this project?

    © 2026 Mushfiqur Rahaman · Building for a sustainable future