Case study 03 · Interactive software
Pocket Arcade
Small games. Clear controls. A choice of pace.
An interaction study
Quick to understand.
Room to find a rhythm.
Illustrative artwork. Explore the live project for the actual games and controls.
A short break should be easy to start.
Pocket Arcade is my personal collection of small browser games. The project explores a different side of software development: how instructions, input, feedback and state combine into an experience a person can understand quickly.
The public site offers fourteen games, with Relaxed and Classic paces. That gives the player a choice about intensity rather than requiring the same timing from everyone.
The detail of the interaction is the work.
Explain the controls in context
Each game needs a clear starting point, relevant control guidance and feedback that makes the current state understandable. A collection also needs a predictable way to return to the game selector and start again.
Make pace a player choice
Relaxed and Classic modes provide different ways to approach a challenge. Best scores are tracked per pace and saved on the device, keeping progress close to the playing experience.
Keep the public experience direct
The browser site offers play without an account and includes an offline download option. The portfolio links to that working experience so visitors can inspect the interaction for themselves.
Inspect behaviour through play.
Useful review points include whether the instructions match the controls, whether restarting resets the game state, and whether the selected pace is clear. Score persistence and returning to the selector are also part of the complete experience.
The live project is the evidence available here. This case study does not claim a formal all-device accessibility certification, a published app-store release or independently measured player outcomes.
Explore Pocket Arcade and its public informationA personal project with a public playing experience.
Pocket Arcade is separate from my employer’s systems and projects. Its source code remains private; this portfolio presents the public site and the interaction decisions it demonstrates.
Device-local progress is not a shared player account or cloud leaderboard. Offline behaviour depends on using the option supplied by the live site.