Tennis & padel platform
My own product: a player app, a club-manager app and the real-time API behind both — designed and built solo, to find out whether I could carry a whole product alone.
Finding a compatible opponent and an available court in Belgrade is spread across phone calls, group chats and separate club systems. Players and clubs need the same information about the same courts, and neither side has it.
Two sides, one state
Both apps share one backend, so a booking made by a player appears in the club’s schedule and drops that court’s availability through the same real-time event stream.
Built solo
I designed and built both frontends and the shared Node API: court booking with multi-slot selection and a running total, matchmaking by rating band and time, and club group chat over REST and WebSockets.
Honest scope
The booking, availability and messaging layer runs. Tournaments, club profiles and parts of matchmaking are high-fidelity prototype UI on mock data, and the player-side confirm is not yet wired to persistence.
A working prototype rather than a launched product, built in fifteen days to see whether product, design, frontend and backend could sit with one person. I came back to it later with AI agents to pressure-test the market and monetisation before deciding what to build next.
NEXT CASEPansuara →