That includes Frontier Settlers, Quizzr, and Calc 1 Atlas.
Bio
Builder of practical web products.
I focus on multiplayer games, study systems, and live operations software that need to stay understandable while people are actively using them.
The through-line is simple presentation over complicated framing: clear state, clear routing, and interfaces that respect attention.
If a user cannot tell what to do next quickly, the design is not finished.
Approach
What I build and how I think about it
The details change from product to product, but the rule is consistent: make the route obvious, make the state trustworthy, and remove anything that gets in the way.
What I Build
Products that have to work in motion.
That means realtime game state, account-backed study progression, live event controls, and utility software that can be opened and used without warm-up.
How I Build
Reduce friction before adding flourish.
I prefer a simple front door, a reliable core loop, and interfaces that feel composed rather than crowded. The visual system should support the product, not compete with it.
Path
A short path through the work
The pattern stays steady: start from a useful tool, tighten the core flow, then simplify the way people enter and resume it.
-
Started from utility
The earliest useful builds leaned toward tools and project pages that could run without a heavy stack wrapped around them.
-
Moved into realtime systems
WebSocket-backed apps became the center of gravity: multiplayer game state, live rooms, progress sync, and event operations.
-
Refined the front door
The public site shifted toward a quieter product shell so people can reach the actual experience without working through bulky presentation layers first.