🎨 Palette: Add explicit empty state for zero high score - #422
Conversation
Added a friendly empty state ("None yet! (Play to set one!)") for when the user's high score is 0, improving system status visibility and onboarding encouragement. Also appended a learning to the UX journal.
Co-authored-by: EiJackGH <172181576+EiJackGH@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
💡 What: Replaced the hidden high score behavior with a visible, encouraging empty state when the score is 0.
🎯 Why: Hiding UI elements when data is empty makes the system state less clear. Providing an explicit empty state acts as a subtle onboarding tool and encourages initial interaction.
📸 Before/After: Before, a new player saw nothing below the game title. Now, they see "Personal Best: None yet! (Play to set one!)".
♿ Accessibility: Improves cognitive accessibility by clearly defining the system state rather than relying on absence to convey meaning.
PR created automatically by Jules for task 8529570251847165073 started by @EiJackGH