Games since the Xbox 360 era
Browser games in React, canvas and three.js, desktop games on PC and Xbox 360 before that, 25+ apps with 3.7 million downloads along the way. Korona Krulów reached 100,000+ players in its first days. Play the demo below: a thirty-second arcade loop with a fixed timestep and a frame budget readout.
Available from November 2026 · Wrocław, Poland (CET), remote
Korona Krulów: React, 400+ actions, a leaderboard, open source, two weeks of evenings, 100,000+ players and ~700 upvotes on Wykop at launch. A game is done when strangers play it, so I build for the launch day, with analytics in place for the day after.
A fixed simulation step, rendering decoupled from it, input latency measured rather than felt, a pause when the tab hides so nobody returns to a dead character. The demo on this page runs exactly that loop and shows its numbers.
Canvas and WebGL, three.js for 3D, Electron for desktop builds, React Native and PWA for phones, the stores handled. Migawki is a three.js game with cutscenes, bloom and synthesized narration served from a Cloudflare Worker.
My own chat network carried 30,000 concurrent users on sharded .NET servers. Rooms, leaderboards, anti-cheat basics and events per level in PostHog, so retention and difficulty curves come from data, never from the loudest player.
Proof
Problem, what I did, result. Client names only where I am allowed to use them.
See also: React · JavaScript
See also: JavaScript
See also: C# & .NET (legacy)
One foot in the door
Two ways to see how I work before you commit to a sprint. Fixed scope, a number in writing after a short call.
I read the repo, CI, tests, security and the parts the team avoids. You get a written report with findings ranked by risk, a plan with milestones and a go or no-go you can defend. I have run this for a large software house before its clients saw the code.
Send me the diff that worries you. Within a few days you get line-level comments, the three things I would change first and whether I would merge it.
Live demo
Catch the green commits, dodge the red bugs. Arrow keys or touch. The readout shows frames per second, frame time and the fixed 60 Hz simulation step the game runs on, independent of your screen’s refresh rate.
Demo loading…
Switch tabs and come back: the game pauses instead of fast-forwarding. That is the loop doing its job.
How it works
You describe the product and the problem. I ask the questions I would ask on day one. If I am not the right person, I say so and point you to someone who is.
A short written plan follows: what we build first, what we measure, how we work together and what it costs. No slide deck.
The first slice ships in the first week: deployed, measured, reviewable. From there the work is paced by what the numbers say.
Fit check
Working style
PostHog in every project from day one. A tracking plan per feature and dashboards leadership actually reads.
Where there is no PM I set priorities directly with the people using the software and answer support myself.
Claude Code and Codex work on main with hooks, lint and test gates. The model suggests, the criteria decide. Every PR gets a human review and AI-assisted content is disclosed.
FAQ
A free 30-minute call. You bring the problem, I bring questions. No prices on this page because scope comes first.
If I am the wrong person I will say so on the call and point you to someone better.
After you book: a calendar invite, then the call. Nothing else to fill in.
Available from November 2026 · B2B contract or employment · Wrocław, Poland (CET), remote
