Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 months ago

Angular Rock Paper Scissors Game

angular, sass/scss, typescript, web-components, bem
Daniel Cristea•40
@gdcristea
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?

I'm most proud of leveraging Angular’s latest features—particularly Standalone Components and Angular Signals—to build a clean, modular Rock, Paper, Scissors game that feels modern and responsive. The use of SCSS for custom styling and CSS animations for interactive effects (like the pulsing hover effect) really helped bring the design to life, and implementing LocalStorage for score persistence added a nice touch for user experience. Next time, I'd invest even more time in cross-browser testing (as I encountered some issues on Safari) and refine my state management approach to further simplify the code and boost performance. I’d also like to explore more robust accessibility features to ensure an inclusive user experience.

What challenges did you encounter, and how did you overcome them?

One of the major challenges was achieving consistent hover effects across browsers, particularly on Safari, where CSS pseudo-elements and pointer events behaved differently. This led to some trial and error with various CSS workarounds to mimic the desired hover effect. Additionally, configuring Angular’s build process presented its own hurdles—especially around polyfills and asset paths—which required careful adjustments and community research to resolve. I also struggled to get the animation to start on its own without any user interaction, which added another layer of complexity. By methodically isolating issues and testing incrementally, I managed to overcome these obstacles, though they highlighted areas for potential improvement in future projects.

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

I'm looking for advice on optimizing the use of Angular Signals for state management—any best practices or patterns that could make the code even cleaner and more efficient would be valuable. Also, I’d welcome suggestions on performance, particularly on lower-end devices, to ensure the game is as smooth and inclusive as possible. Any insights or recommendations in these areas would be greatly appreciated.

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 Daniel Cristea'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
Frontend Mentor logo

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 1st-party linked stylesheets, and styles within <style> tags.

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.