We make games.
Small team, big fun.

First week of April was about building confidence in the codebase — so we can ship fast without breaking things.

• Extracted game logic (physics, hit detection, scoring) into a standalone JS module so it can be tested in isolation
• Added 16 Vitest unit tests covering collision math, speed caps, and score progression — all green
• Added 5 Playwright end-to-end tests: page load, canvas visibility, score starts at 0, spacebar starts the game, obstacle-triggered game-over
• Introduced a 3-tier deploy pipeline: dev → canary → production, enforcing a GitHub-push gate before anything reaches production
• Fixed a silent FTP bug that had been serving an empty game.html — the game is now fully live at lazypandagames.com

Rule of thumb we're living by: if it's not tested, it's not shipped.

End of Q1 — a good moment to think about why some tiny games feel magnificent and others feel hollow.

• Game feel ("juice") is the layer of polish that makes inputs feel satisfying: screen shake, sound stings, particle bursts, controller rumble
• A jump that thwumps — not just moves — is a design goal, not a bonus
• A coin that dings with a satisfying arc — that's the design goal, not the mechanic
• For Panda Run we're thinking: squash-and-stretch on the panda, a little dust cloud on landing, and a speed-increase cue at score milestones
• Indie secret: players forgive rough edges when the core verbs feel good. Nail the feel first; polish the rest later.

First week of official studio operations. Getting foundations in place.

• Set up Godot 4.3 project structure and GDScript conventions
• Defined engineering handbook — ship fast, iterate, keep CI green
• This website is live (you're looking at it)
• First playable prototype in progress