Verified discovery
Filter venues, inspect map locations, and view only published, verified listings.
Community / App case study
Kabacan PicklePlay
A local court-discovery and booking prototype with verified-listing gates, schedule-based availability, server-authoritative pricing, atomic double-booking protection, and owner and administrator workflows.
Court-discovery and reservation prototype
- Laravel
- PHP
- Blade
- Alpine.js
- Leaflet
01 / Overview
What it’s built for.
Make local court discovery and reservation requests depend on verified venue facts, generated schedules, and server-authoritative booking rules.
Who it serves
Players, participating court owners, and listing administrators.
02 / Features
Inside the app.
Reservations
Choose generated slots, request a booking, submit payment references or private proof, and track statuses.
Owner and admin tools
Manage schedules and blackouts, review bookings and payment evidence, and gate listing publication.
03 / Workflow
From task to outcome.
An owner prepares a court listing and verification evidence.
An administrator reviews required facts before publication.
A player chooses an available slot and submits a reservation.
The owner reviews the request and payment evidence, then tracks completion.
04 / Technical layers
How the pieces work.
Blade · Alpine.js · Tailwind · Leaflet
Player and owner pages use OpenStreetMap-backed venue maps and responsive booking screens.
Laravel · PHP
Schedule generation, authoritative prices, locks, and atomic operations prevent double booking.
SQLite locally · MySQL/MariaDB option
Bookings, venue facts, and audit records are separate from authorization-protected proof files.
Laravel roles · Email verification
Listings and file reads are gated by publication evidence and the requesting user’s permissions.
05 / Limitations
What to keep in mind.
- The seeded reference venue is a non-public draft with unconfirmed facts left blank.
- Payments use references or proof review; a real payment gateway is a documented future addition.
- Live venue availability requires participating owners and verified schedules.
06 / Evidence
Follow the source.
These descriptions were reviewed against the linked source snapshot on October 12, 2026. Repository code and documentation may evolve after this review.