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

TicTacToe_React_TypeScript_Tailwind

react, shadcn, tailwind-css, typescript, framer-motion
P
Julien Gilbert•500
@juliengDev
A solution to the Tic Tac Toe 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?

Key Features:

  • Two Game Modes: Play against an AI or with a friend
  • Adjustable CPU Difficulty: Beginner, Intermediate, and Hard (default: Hard)
  • Persistent Score Tracking: Keeps track of wins, losses, and ties
  • Smooth Animations: Enhances user experience
  • Fully Responsive: Works on all screen sizes
  • Modern UI/UX: Built with cutting-edge libraries

First time I've used shadcn/ui, styling a component from the library to match the design of the model. I was able to add an animation that adds value to the overall experience of the application.

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

Implementing the different game algorithms, and in particular the cpu mode, wasn't easy, so I had to go and find some external code to develop the functionality. Managing the different states is also complex throughout the application.

The project is Built with :

  • Vite - Fast development environment
  • React - Modern UI framework
  • TypeScript - Strongly typed JavaScript
  • React Router DOM - For navigation and error handling
  • Tailwind CSS - Utility-first styling
  • Shadcn/UI - Custom UI components
  • Framer Motion - Smooth animations
  • Zustand - Global state management
  • Lucide - Icon library
What specific areas of your project would you like help with?

I know that some effects are missing at the end of the game to bring out the winning combination, but I'll come back to this later. 99% of what was expected is there, and as usual I'm open to any suggestions for improvements. Thanks in advance.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Tsotne Meladze•1,120
    @tsotneforester
    Posted 3 months ago

    just remove this huge vertical scroll 😅 and on netlify if using react router you must include _redirects file in public folder to make routes work.

    https://juliengdev-tictactoe.netlify.app/ - returnes "page not found"

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 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.

Oops! 😬

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

Log in with GitHub