The Board Came Back: Lessons in Persistent UI State

In a recent post, developer Michael Truong discusses the challenges of managing persistent state in his web game, Codenames AI. Truong highlights a common pitfall: assuming that all UI state should be saved and restored upon page reloads. He discovered that while users expect drafts like typed text to persist, ephemeral 'thinking aids'—such as card highlights used during clue drafting—should not be treated as part of the game's permanent state. When these highlights were incorrectly persisted, they leaked across different game modes, creating a misleading user experience. Truong argues that the persistence boundary must be semantic rather than architectural. Developers should explicitly define what constitutes 'current truth' in their application's snapshot, ensuring that proposals and temporary UI hints are discarded while accepted work is preserved. He emphasizes that testing should focus on behavioral outcomes rather than just verifying that a save file loads.