Turf

# AI App Builder Prompt — Turf Booking & Player Matching Platform Build a modern full-stack web and mobile-first application for a sports turf booking and player matching platform. The application should solve the real-world problem where users currently need to physically visit turfs or call turf owners to check slot availability for cricket and football grounds. The platform should support 3 major roles: 1. Player/User 2. Turf Owner 3. System Admin The application should have a clean modern UI similar to modern SaaS applications with responsive mobile-first design. Preferred style: * Dark + light mode * Modern sports-tech aesthetic * Smooth animations * Real-time updates * Clean cards/grid layouts * Professional dashboard UI Tech preferences: * Frontend: React (typescript) * Backend-ready architecture(fastAPI) * PostgreSQL-compatible schema * Realtime-ready structure using WebSockets * Mobile responsive * API-first architecture --- ## CORE FEATURES # 1. USER / PLAYER FEATURES ## Authentication * Phone OTP login * Google login * Email/password login * JWT-based auth * Role-based authentication ## User Profile Fields: * Name * Profile photo * Mobile number * City * Preferred sports * Skill level * Bio ## Home Page Show: * Nearby turfs * Popular turfs * Available matches * Open player slots * Recommended games ## Turf Discovery Allow search by: * City * Area * Sport type Filters: * Price range * Rating * Indoor/outdoor * Available now * Time slots * Distance ## Turf Details Page Show: * Turf photos gallery * Turf name * Address * Map integration * Sports available * Slot pricing * Available slots * Booked slots * Amenities * Ratings and reviews ## Slot Booking System Flow: * Select turf * Select date * Select slot * Confirm booking * View booking confirmation Booking states: * Pending * Confirmed * Cancelled * Completed ## Booking History Show: * Upcoming bookings * Past bookings * Cancelled bookings ## Notifications * Booking confirmation * Slot cancellation * Match join updates * Turf reminders --- ## UNIQUE FEATURE — PLAYER MATCHING Create a “Find Players / Join Match” feature. This is the core differentiator. Scenario: A user books a cricket or football turf but needs additional players. Example: * Cricket match needs 10 players * Organizer only has 7 players * They create 3 open player slots Other users can: * Browse open matches * Join available games * See location * See skill level * See player requirements * Request to join ## Open Match Module Fields: * Match title * Sport type * Turf * Match timing * Required players * Skill level * Cost per player * Public/private visibility ## Join Match Feature Users can: * Request to join * Get approved * View participants * Leave match ## Match Cards Display: * Sport * Turf * Time * Distance * Players needed * Skill level * Price split --- # 2. TURF OWNER PANEL --- Create a dedicated dashboard for turf owners. ## Turf Owner Features ### Turf Registration Allow owners to: * Add turf details * Upload images * Add sports supported * Add slot timings * Add pricing * Add amenities ### Turf Management * Edit turf details * Enable/disable turf * Manage slot availability * Block maintenance days ### Booking Management Show: * All bookings * Upcoming bookings * Booking status * Customer details ### Dashboard Analytics Show: * Total bookings * Daily bookings * Monthly revenue * Popular timings * Peak hours --- # 3. ADMIN PANEL --- Create a modern admin dashboard. ## Admin Features * Manage users * Manage turf owners * Approve/reject turfs * Ban/report users * View analytics * Handle disputes * Monitor bookings ## Admin Dashboard Widgets Show: * Total users * Active turfs * Total bookings * Revenue stats * Open matches count --- ## REALTIME FEATURES Implement realtime-ready architecture. Use realtime updates for: * Slot availability * Booking updates * Match joining * Notifications Avoid page refreshes. --- ## DATABASE STRUCTURE Design scalable database models for: * Users * TurfOwners * Turfs * TurfSlots * Bookings * OpenMatches * MatchParticipants * Reviews * Notifications Relationships should be production-grade and scalable. --- ## UI/UX REQUIREMENTS Design inspiration: * Airbnb * Playo * BookMyShow * Modern SaaS dashboards Use: * Modern cards * Smooth hover effects * Sports-themed UI * Clean typography * Rounded corners * Minimal but premium design Pages required: * Landing page * Login/signup * Turf listing * Turf details * Booking flow * User dashboard * Turf owner dashboard * Admin dashboard * Open matches page * Notifications page * Profile page --- ## ADVANCED REQUIREMENTS * Role-based routing * Protected routes * Scalable folder structure * Clean reusable components * Responsive on mobile/tablet/desktop * API integration ready * SEO-friendly structure * Production-ready architecture --- ## MVP PRIORITY Build these first: 1. Authentication 2. Turf listing 3. Slot booking 4. Turf owner dashboard 5. Real-time slot updates 6. Open player matching Keep payment integration disabled for now but make architecture payment-ready for future integration. --- ## OUTPUT EXPECTATION Generate: * Full UI/UX * Frontend pages * Backend architecture * Database schema * API structure * Reusable components * Dashboard layouts * Modern responsive design * Production-ready codebase structure The application should feel like a scalable startup product, not a basic college project.