Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

Rock-Paper-Scissors-Game

Jonathan Peters•230
@QMS85
A solution to the Rock, Paper, Scissors game challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

What I'm Most Proud Of...

Clean Architecture & Code Organization:
The implementation uses a well-structured class-based approach with the RockPaperScissors class that encapsulates all game logic, making the code maintainable and easy to understand.

Responsive Design:
The CSS implementation includes comprehensive mobile-first responsive design with detailed breakpoints (768px, 375px) that ensure the game works well across all device sizes.

Complete Feature Implementation:
Successfully implemented all core features including:

  • Game logic with proper win/lose/tie detection.

  • Score persistence using localStorage.

  • Smooth transitions between game phases.

  • Interactive rules modal.

  • Keyboard accessibility (ESC key to close modal),

  • Visual Fidelity:
    The styling closely matches the Frontend Mentor design specifications with proper gradients, shadows, and layout positioning.

What I Would Do Differently Next Time.

Enhanced Animation & Feedback:
Add more visual feedback like:

  • Animated transitions when switching between selection and result phases.
  • Winner highlight effects with pulsing or glow animations.
  • Delayed reveal of the house choice to build suspense.

Better Error Handling:
Implement more robust error handling for:

  • localStorage access issues.
  • Missing SVG icons.
  • Browser compatibility checks.

Code Optimization:

  • Extract magic numbers (like choice dimensions, delays) into constants.
  • Create a more modular event handling system.
  • Add JSDoc comments for better code documentation.

Accessibility Improvements:

  • Add ARIA labels for screen readers.
  • Implement focus management for keyboard navigation.
  • Include sound effects with audio controls.

Extended Features:

  • Add the bonus Rock, Paper, Scissors, Lizard, Spock variant.
  • Implement game statistics (wins/losses over time).
  • Add difficulty levels or tournament modes.
What challenges did you encounter, and how did you overcome them?

Responsive Design Complexity
Problem: Creating a layout that works across desktop, tablet, and mobile while maintaining the triangular arrangement of choices.

My Solution: I Used CSS Grid with careful breakpoint management:

Desktop: 2-column grid with rock spanning both columns
Mobile: Single column with reordered elements for better UX
Implemented mobile-first approach with progressive enhancement

The key to overcoming these challenges was breaking the problem into smaller, manageable pieces and implementing a clean separation of concerns between presentation, state management, and game logic.

What specific areas of your project would you like help with?

Accessibility Improvements

Error Handling: The code currently has minimal error handling.

My Specific questions would be:

  1. How to handle cases where SVG icons fail to load?
  2. What to do if localStorage is disabled or full?
  3. How to gracefully handle DOM manipulation errors?
Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Jonathan Peters's solution.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.