COURT BOOKINGLIVE · LOCAL BACKEND
The player sees aggregated availability across the club's courts, selects one or more time slots and gets a running total - served live by the shared backend. Right: the 14-second recording of the real flow.
WORKING PROTOTYPEINDEPENDENT PRODUCT · TWO-SIDED PLATFORM
Tennis Platform
A two-sided tennis platform for Belgrade - players find matches and book courts, clubs manage their calendars in real time. Conceived, designed and built solo: a player app, a club-manager app and the shared real-time backend.
01 - THE IDEA
One product for both sides of the court.
Finding a compatible opponent and an available tennis court in Belgrade is fragmented across phone calls, group chats and separate club systems. The concept combines finding an opponent, booking a court, tournaments and club communication in one player app - with a second experience for clubs managing courts and bookings.
From home, everything starts with one sheet: find a match, or reserve a court.02 - THE PLAYER EXPERIENCE
Real screens from the running prototypeMATCHMAKINGPROTOTYPE UI · MOCK DATA
Open matches can be explored by rating range, club and time, with the cost of the court shown per player.
MESSAGINGLIVE
Club group chat over REST + WebSocket - admin announcements, read receipts.
04 - MORE THAN A BOOKING SCREEN
A considered product environment, not one screen.
Tournaments, messaging and club profiles are high-fidelity prototype UI on mock data; the admin chat runs on the live messaging layer.
05 - HOW I BUILT IT
Built solo as a product prototype.
I conceived the product, designed the player and club experiences, and built both frontends and the shared backend.
PLAYER APPReact · TypeScript · Vite · Tailwind
CLUB MANAGERReact · TypeScript · Vite · Tailwind
BACKENDNode · Express · WebSockets
2 apps + shared real-time API~13.7k lines TS/JS43 commits15-day build
AND LATER - PRODUCT RESEARCH
Coming back to the idea later, I used AI agents to pressure-test the market, product assumptions and monetization before deciding what I would build next. The agents proposed; I made the final calls.
STATUSWorking prototype. The real-time booking / availability and messaging layer works locally; several broader product surfaces remain high-fidelity prototype UI rather than fully wired features.
