Hints are a UX problem disguised as a content problem. On a daily puzzle, a hint that gives away the answer is worse than no hint at all: it converts a solve into a lookup and removes the reason the player returned.
Poople handles this with a layered hints system. The first hint nudges a direction without naming a word. Later hints narrow the space. The full answer is a separate decision, not a side effect of clicking the hint button.
A few principles I have seen work in practice on that site and would reuse anywhere:
- Hints should be ordered by information, not by difficulty. The first hint is the cheapest nudge and the last one is the near-answer. Players take them in sequence.
- The hint must be useful without being final. A directional nudge restarts thinking; a word replacement ends it.
- The answer must be one clear click away. If a stuck player has to dig through UI to give up, they will just close the tab.
You can see the actual wording they use on the hints page. It is worth reading as an example of copy that does interface work: each line changes what the player can do next without telling them what to do.
The broader lesson is that daily games are not hard to build. They are hard to balance. A hints system is where that balance lives, and it deserves a design pass rather than a single "reveal answer" button.