"# {NitroType-Solo} Project Report
1. The Concept
{NitroType Solo} is a lightweight, web-based typing racing game where the player races against an AI car by typing faster and more accurately. I chose this project for a one-day sprint because it combines simple gameplay with real-time state management, UI polish, and responsive design. The goal was to make typing practice feel more like an arcade racing game than a traditional typing test.
2. The Stack
The Stack: HTML5, Vanilla CSS, and JavaScript.
The AI Assist: ChatGPT helped with the initial product planning and generated the technical direction for the game. OpenAI Codex was then used for the coding phase, turning the handoff document and design requirements into a playable browser game with race logic, typing logic, AI movement, local storage records, and polished game screens.
3. The 1 Day Sprint:
Morning (Hours 1–3): We started by defining the core idea: a solo typing race against an AI opponent. The first few hours focused on planning the game loop, difficulty levels, typing mechanics, AI speed, win/lose conditions, and the required screens. The project direction was documented clearly so development could move quickly.
Afternoon (Hours 4–6): The coding phase began. Codex built the core game in a single HTML file using vanilla JavaScript. The first version included the start screen, typing engine, AI car movement, progress tracking, race results, and local storage records. After the basic game worked, most of the time was spent improving the UI to feel more like a retro arcade racing game. The Finish Line (Hour 7-8): The final hours focused on polishing the visual experience. We redesigned the start screen, play screen, win popup, lose popup, pause popup, HUD, buttons, spacing, and mobile responsiveness using the existing pixel-art assets. The goal was to make the game feel cohesive, responsive, and closer to a commercial mobile game style.
4. The Roadblocks
Roadblocks: The biggest roadblock was UI precision. The gameplay logic came together fairly quickly, but matching the mockups closely required many small iterations. Spacing, button alignment, mobile HUD behavior, popup proportions, and pixel-art styling all needed manual refinement. Another challenge was keeping the work scoped. Each screen needed to be improved without accidentally rewriting the typing engine, race logic, AI behavior, or local storage. The project required careful changes so the visuals improved while the game continued working correctly.
5. Key Takeaways
What worked best? The core gameplay loop. The idea of typing to move a car forward is simple, easy to understand, and immediately playable. The AI opponent also makes the typing experience feel more exciting than a normal practice tool. What worked worst? Pixel-perfect UI matching. Even when the assets existed, getting the layout to match the mockups across desktop and mobile took repeated adjustment. Small spacing or alignment issues made a big difference in how polished the game felt.
My final thought: If I had one more day, I would add sound effects, stronger race feedback, and more visual effects when the player types correctly or wins. I would also continue refining the responsive layout so every screen feels perfectly tuned on small phones.