Mohammad Awayssa
All work

World Cup Matches

When is the next game?

World Cup Matches on desktop, with a next-match countdown and navigation to the tournament schedule, groups and knockout stage.

The website during the 2026 tournament. Match details are part of the original screenshot.

A question worth building around.

I wanted a simple way to see how long remained until the next match. I found a free football API through a GitHub repository and used Codex to build a website around match information and countdowns.

It was a personal experiment: take something I was interested in and make a useful thing out of it.

Before kickoff. During the match. On your phone.

The countdown became part of a wider match hub: the tournament schedule, group standings, knockout rounds and live-score views. Match times are shown in the visitor’s local timezone.

English and Arabic views made the same information available in both languages, including a right-to-left mobile schedule. These screenshots show the website as I used it during the tournament.

The Arabic desktop interface showing two match score panels under a live-match heading.
Live-score view in Arabic, captured during the tournament.
The Arabic mobile schedule with date filters, teams, kickoff times and venues.
The mobile schedule in Arabic, with date filters and match details.
The English mobile next-match countdown with team flags, kickoff time and venue.
The countdown on a phone. Original tournament screenshots can be opened at full size.

The interface is mine. The football data comes from elsewhere.

The original free API I found on GitHub was livescoreFootball by rezarahiminia. It gave me the external football data source to start building the match hub.

The current public repository stores the tournament schedule locally and includes a server-side live-scores function that requests football-data.org and worldcup26.ir. It normalizes the providers’ match data and can use a successful feed when the other request fails.

The football-data.org key stays on the server. The site combines these external sources with the schedule; I did not create the underlying football APIs. The implementation was generated with Codex as part of the same assisted workflow.

Honest about the process.

Codex generated most of the implementation. My contribution was the idea, finding the API, directing the build and trying the result.

This project represents curiosity and experimentation. It is not presented as evidence that I manually wrote or fully mastered the entire codebase.

Tools & context

  • React
  • Vite
  • Tailwind CSS
  • JavaScript
  • Vercel Functions
  • External football data
  • Codex