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

Responsive Rock, Paper, Scissors App using HTML, CSS, JS, TS and React

react, typescript, animation
Jaime Contemprato•90
@Jaime-Cont
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 is that I can take on more difficult challenges, I'm proud that I was able to quite easily think of how to accomplish this advanced challenge and I'm proud that I learned from my previous challenges and incorporated them onto this challenge again!

I'm also proud of incorporating TypeScript, Vite and React into this challenge!

If I were to do anything differently next time it would be to use React hooks, I thought of learning and using them here but I wasn't familiar with them so I avoided it, but now, I'm ready to take on the challenge and learn more React!

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

The challenges I encountered include:

  • Not being knowledgeable in functions when using React.
  • Not knowing how to reference a HTML Element in TypeScript. I overcame them by:
  • Researching on how to properly create and use functions in React using arrow functions.
  • Researching how to reference and create HTML Elements references in TypeScript for tinkering with HTML Elements using functions.
What specific areas of your project would you like help with?

The areas in my project I would like help with would probably be the following:

  • How to use React hooks in my application, I know there is a lot more better ways in tackling the challenge, and I know using hooks would be a better way to go, but being unfamiliar with it I would love help with that.
  • TypeScript and the proper way of coding in TypeScript, I think I did a good job, but I think there are more better ways to do it.
  • Better CSS, like Tailwind CSS, which I'm starting to familiarize myself with but still no proper practice on it and would like to be taught it for future projects!
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 Jaime Contemprato'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.