إيفو سبورتس

The client

EvoSports is building a home for local sport: players discover venues, book a court and follow the places they play; venue owners manage courts, prices and bookings.

What they needed

Players book a court in a few taps, and never arrive to find someone else booked it too.
Owners set their own courts, slot lengths, prices and booking windows.
A console for the EvoSports team to run venues, content and reports.
Arabic and English across every screen.

What we built

Part	What it does
Mobile app	For players: discover venues, see live availability, hold a slot, check out, see "my bookings", follow venue updates. For owners: an owner mode to manage their venue.
Admin console	Venues, owners, content, reports and settings for the EvoSports team.
Backend & API	Availability, holds and bookings, accounts, permissions, files and notifications, shared by both apps.

How it fits together

flowchart LR
    Mobile[Mobile app<br/>players & owners] --> API[Backend & API]
    Console[Admin console] --> API
    subgraph Foundations[Shared foundations]
        Auth[Sign-in & one-time codes]
        Lang[Languages, editable without a release]
        Perm[Permissions, checked on the server]
        Files[Files, private by default]
        Notify[Notifications]
    end
    API --> Foundations
    API --> DB[(Database)]

A booking, from the system's side:

The player opens a venue and sees live availability per court.
They tap a slot. The backend holds it for 5 minutes. If two players tap at the same second, the database lets exactly one win.
They check out. The hold becomes a booking only if it is still theirs and still valid.
The owner sees the booking in owner mode; the player sees it under "my bookings".

How we worked

Plan: every feature starts from the signed agreement, kept word for word. Open questions were settled before building: 59 of them for the venues part alone.
Build: the platform stands on shared foundations (sign-in, languages, permissions, files) that were already proven in production.
Measure: 1,414 automated tests run on every change, and every requirement is traced to the part of the API that delivers it, so "how much is ready?" always has a number.
Learn: what we learned here we wrote up, from handling permissions end to end to building Arabic screens properly.

Status

In active development. The venues and booking features are built and running on staging; the next features follow the same path.