A personal arcade of playable browser games on Next.js. Game loops, input handling, collision, and score state built in React and TypeScript, with attribution clearly marked for anything not written from scratch.
Stack, status, evidence, and public actions are rendered from the typed project record.
Category
Frontend Experience
Type
Website
Priority
Supporting
Overview
What this project is
A personal arcade of playable browser games on Next.js. Game loops, input handling, collision, and score state built in React and TypeScript, with attribution clearly marked for anything not written from scratch.
Problem
Why it matters
Games are the hardest interfaces to fake. Input, timing, collision, and state either work at 60fps or they visibly do not.
Solution
Approach
A collection of playable browser games under one platform, built as real-time frontend engineering practice with transparent attribution.
Architecture
System shape and stack
Engineering
Real-time constraints in the browser
Each game handles its own loop, input, collision, and score state in React, which forces correctness and performance habits that static pages never test.
Integrity
Attribution built in
Anything externally sourced, embedded, or open source is identified as such, so the original engineering work stands on its own.
- TypeScript
- React
- Next.js
Technical Highlights
Visible technical signal
- Multiple playable browser games on one platform
- Game loops, input, and collision handled in React
- Clear attribution for any external work
What It Proves
Builder signal
Real-time frontend engineering: game loops, input handling, and state kept correct under a frame budget.
Boundaries
Context that should stay visible
Do not overclaim third-party, embedded, or open-source game work. Public UI must call out exceptions clearly when reviewed.