What I Learned Building a Daily Football Player Guessing Game

I started building a daily football guessing game because I wanted something that could be played in a few minutes without turning football knowledge into a giant trivia exam. The simple version sounded obvious: choose a hidden player, let people search for names, and show clues after each guess. The difficult part was making every wrong answer useful.

A guess has to reduce uncertainty

If a player guesses a famous striker and only sees "wrong," the game is mostly luck. The feedback becomes interesting when it shows consistent differences such as league, club, nationality, age, position, or shirt number. A failed guess should produce a better second guess.

Football data is messier than it looks

Player names have accents, clubs change, leagues use different labels, and a footballer can appear under several positions. Search suggestions need to be forgiving without becoming vague. Long names also create layout problems on mobile, especially inside compact clue grids.

The daily puzzle needs one shared clock

A daily game feels broken if two friends receive different answers on the same date. I had to treat the puzzle date, timezone, attempt limit, and completion state as part of the game rules rather than implementation details. Refreshing the page should not silently change the challenge.

Sharing should not spoil the answer

The result needs to communicate how the run went without exposing the footballer. A compact pattern is more useful than a sentence containing names, because people can compare attempts while the puzzle remains playable for everyone else.

The current version is available as Wordle Cup Football. It is still a small browser game, but building it changed how I think about daily puzzles: the interface should make the first action obvious, every mistake should teach something, and the final result should be easy to share.