Build
FIFA World Cup 2026 Live Calendar
Live scores and fixtures in your calendar — subscribe once on iPhone, Google, or Outlook. No app, no login, no manual refresh.
What I built
A serverless live calendar for all 104 FIFA World Cup 2026 matches. Subscribers add it once to iPhone, Google, or Outlook and get live score updates, goal scorers, and venue info directly in the calendar event title and description.
No app, no login, no manual refresh. The knockout bracket auto-resolves as teams advance — so Round of 16, quarters, semis, and the final stay correct without anyone touching a spreadsheet.
World Cup 2026 is happening now. People want match info without installing another app. This was a real problem worth solving — and a strong proof of concept for the serverless + Cloudflare Workers stack.
How I built it
Built on Cloudflare Workers + KV with three cron jobs. Subscriber requests only read from KV — so 10,000 subscribers cost the same API quota as one. The worker fetches match data on a schedule, normalises timezones (ET, CDT, PT, Vancouver), and writes updated ICS feeds that calendar apps poll.
Scope evolved naturally: simple calendar first, then a schedule page, then live scores, then real-time updates. Each step felt obvious once the previous one worked. Most of the ~11 hours was architecture, prompt writing, and verification — not typing code.
What surprised me
Two things stood out.
Building something simple is often just the starting point. I started with a basic calendar, then added a schedule page, live scores, and real-time updates — each felt obvious once the last piece was working.
The gap between “AI can build anything” and actually deploying is wider than the hype suggests. Getting timezone handling right, fixing a quarter-final sort bug, verifying all 104 fixtures — that work still falls on you. AI writes the code; you own the correctness.
Next time I’d front-load the architecture doc before opening Claude Code. A clearer upfront spec would cut a lot of back-and-forth.
Follow the build log
I publish each build openly — tools, decisions, and what surprised me along the way.