Arcade

Small games. Real interaction practice.

I build web games on the side because they are a great way to practice interface design, state management, feedback loops, motion, and the tiny details that make software feel alive.

01Playable experiments

Small games built to practice interaction design and feedback loops.

02Front-end craft

State, controls, responsiveness, motion, and performance in a playful format.

03Take a break

Try Submit Happens, Riddl, or Dev Wars between project reads.

Choose a game

A few playable experiments

These projects sit alongside the portfolio as small, self-contained games. Some are polished, some are experiments, but each one teaches me something about building better interactive experiences.

Time-entry game

Submit Happens

A playful timesheet drill about logging the week, managing vague requests, and submitting before patience runs out.

Play Submit Happens

Word puzzle

Riddl

A daily riddle game where clues, deduction, and a little persistence help you find the answer.

Play Riddl

Arcade game

Dev Wars

A playful side project built for quick sessions, pixel energy, and a break between portfolio pages.

Play Dev Wars

Why games?

Play exposes the quality of an interface quickly.

Games make interaction design impossible to hide. Feedback needs to be immediate, controls need to feel natural, and the experience needs to stay understandable even when the user is focused on the challenge.

That same thinking carries back into product work: clear states, fast feedback, accessible controls, and interfaces that respect the person using them.

The arcade is a place for those experiments to live without turning the main portfolio into a game site.

Next step

Want the serious work again?

The selected work page shows how the same care for interaction, systems, and usability appears in client and product projects.