Back to work
React / Frontend DemoFrontend demo

Small React frontend demo

React Tic Tac Toe Game

A small interactive React game hosted as a frontend demo.

Project summary

Built a small React Tic Tac Toe demo to show frontend interactivity, state handling, simple game logic, and deployment practice.

A hosted React game demonstrating frontend state and interaction.

Abstract tic tac toe game board illustration

Project summary

Demo URL

ttt.abuhurarrah.com

Project type

Small frontend demo

Built a small React Tic Tac Toe demo to show frontend interactivity, state handling, simple game logic, and deployment practice.

Buyer-facing summary

Client problem

This was not a client problem; it was a compact demo to show frontend state and interaction.

What I delivered

I built and hosted a small React Tic Tac Toe game with interactive UI behavior.

Business result

The project adds light frontend proof while keeping the portfolio focused on stronger client and backend work.

Problem

This project is a small React demo, useful for showing interactivity and deployment practice.

It belongs at the bottom of the work hierarchy because the stronger conversion proof is in WordPress plugins, APIs, automation, and backend/search systems.

This should remain a lower-priority case study because it is a small personal demo.
It is useful for showing React interactivity, not for proving large product delivery.

What I built

Interactive game state

Built the game around React state updates and simple turn/win behavior.

Hosted frontend demo

Published the game as a small live demo so reviewers can interact with it directly.

Interactive game UIReact state managementSimple game rulesHosted demo

Technical decisions

The game is intentionally simple: clear state transitions, game rules, and interactive UI feedback.
It is included as a frontend demo rather than a conversion centerpiece.

The project is intentionally small, so the public copy should stay modest.

Its value is quick interaction proof, not a claim of complex product engineering.

Outcome

The demo gives a quick frontend proof point.
It rounds out the portfolio without pulling attention away from client-facing technical work.

What I would improve

If I expanded it, I would add polish such as keyboard support, move history, or a small AI opponent.

For this portfolio, keeping it small and honest is better.

Tech stack

ReactFrontend StateDeployment

Next step

If you need similar work, let’s talk through the constraints first.

The useful part of a project like this usually starts before code: understanding what the CMS should own, what should live in a backend service, and where integrations or automation can stay maintainable.

Start a conversation