WebTennis Liga

A tennis manager game to play with friends

Each player manages one athlete, trains in skill minigames and competes in a closed league with one match a day. Features playoffs, auctions, chat and match replays, updated live over WebSocket.

Platforms
Web · Game
Year
2026
Status
Closed beta
Role
Game design and full stack

A persistent tennis manager to play with friends. Each person creates and looks after one athlete in a closed league of eight, and the daily loop repeats: tweak the game plan, train in a minigame, watch the 7 p.m. match and understand the result to improve athlete, gear and team.

The clock is shared: plans lock at 6:55 p.m. and the round starts at 7 p.m. for everyone, with each match simulated once on the server and played back live on the phone, with no spoilers. Weekends bring playoffs; between sets, a skill duel.

What the system does

  1. Live daily match

    A 7 p.m. round on a clay court in 2D and 3D, point-by-point scoreboard, plays and stats, and a replay for those who missed it.

  2. Game plan

    Stance, serve, position, rhythm, pattern and gear define how the athlete plays, with a countdown until plans lock.

  3. Nine training minigames

    Serve, forehand, backhand, volley, smash, footwork and more, built with three.js. Results turn into progress points on the athlete's attributes.

  4. League, playoffs and cups

    Weekly table and season ranking, Gold and Silver weekend playoffs, the Open Cup and the Infinite Cup.

  5. Athlete economy

    Prize money, salaries, sponsorships and brand reps, day-by-day balance and statement, plus a staff and gear market with auctions.

  6. Feed and chat

    League feed with commented results, round predictions, press conference and real-time chat over WebSocket.

How it was built

Frontend
Vue 3TypeScriptInertia 3Tailwind 4three.js
Backend
Laravel 13PHP 8.4FortifyReverbHorizonPest
Data
PostgreSQL 17Redis 7
Infra & DevOps
Docker

Technical challenges

  1. An authoritative timeline

    Each match is simulated once on the server and stored as a timeline. The app only reveals what the league clock has already passed, so nobody sees the score early, not even by reloading the page.

  2. Skill inside a manager

    Minigames and duels have to be fun without breaking the simulation: the server validates every run and turns performance into progress within daily limits.

  3. Money that never breaks

    Credits and Bolles are separate currencies, one for the game and one purely cosmetic, with no pay-to-win. Prize, salary and auction accounting is recorded in a statement and covered by tests.

  4. Real time without depending on it

    Chat, duels and auction alerts arrive through Reverb, but everything works without the live connection: the next page load shows the correct state.

Need something
like this?

Tell me the idea or the problem. I help shape the solution and build it from the API to the app.

Let's talk