Skip to content

🎨 Palette: Improve score readability and game-over context#135

Open
aidasofialily-cmd wants to merge 1 commit intomainfrom
palette/ux-score-readability-3421603949046176275
Open

🎨 Palette: Improve score readability and game-over context#135
aidasofialily-cmd wants to merge 1 commit intomainfrom
palette/ux-score-readability-3421603949046176275

Conversation

@aidasofialily-cmd
Copy link
Copy Markdown
Owner

This PR introduces small but impactful micro-UX improvements to the SPEED CLICKER game:

  1. Readability: Scores now include thousands separators (e.g., 1,234) instead of raw numbers, making them much easier to read at a glance.
  2. Visual Polish: The live score line now uses the ANSI \033[K (Erase in Line) sequence. This ensures that when the score or status message changes length, no leftover characters from the previous update remain on the screen, providing a much cleaner "tactile" feel.
  3. Achievement Context: When a player breaks their personal record, the game-over screen now explicitly shows their previous best score (e.g., "You beat your previous best of 10!"). This provides meaningful context and enhances the user's sense of accomplishment.

Accessibility: Improved numeric readability is a key accessibility win for users with cognitive or visual impairments. The use of standard ANSI clearing sequences improves compatibility across different terminal emulators.


PR created automatically by Jules for task 3421603949046176275 started by @aidasofialily-cmd

- Added `formatWithCommas` helper for thousands-separator formatting of scores.
- Improved live score display with `\033[K` (Erase in Line) for cleaner UI updates.
- Enhanced Game Over screen to display the previous personal best for better achievement context.
- Verified terminal cursor handling with `verify_ux.py`.

Co-authored-by: aidasofialily-cmd <247843425+aidasofialily-cmd@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant