🎨 Palette: Add explicit empty state for high score#326
Conversation
Added a simple message ("None yet - go set one!") when the high score is 0, rather than hiding the element entirely. This improves the onboarding experience by clarifying the system state and gamification features.
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: Added an explicit empty state message ("None yet - go set one!") for the Personal Best display when the score is 0.
🎯 Why: Previously, if a user had no high score, the entire Personal Best display was completely hidden. In terminal applications, hiding UI elements when data is absent can leave the user unsure of the system state or unaware that a feature exists. Providing an explicit, encouraging empty state clarifies the system state and improves user onboarding.
📸 Before/After:
Before: [No output for Personal Best if score is 0]
After:
Personal Best: None yet - go set one!♿ Accessibility/UX: Improves the initial user experience by providing clear feedback on the current state of the application's achievement system.
PR created automatically by Jules for task 7317332222582443411 started by @EiJackGH