Learn / Browser games
Build browser games that feel finished.
Most AI-generated games fail on feel and performance, not on ideas. This is the production framework that closes that gap.
Framework
Core loop to launch
- 01
Core loop
One verb, repeated, that stays interesting for 60 seconds.
- 02
Game feel
Input response, timing, feedback and readable state changes.
- 03
Art direction
A consistent limited palette beats expensive assets.
- 04
Performance
A frame budget you measure, not a hope.
- 05
QA
Collision, input, resize and touch behaviour, tested deliberately.
- 06
Launch
Export, host, share, then watch real players.
2D or 3D in the browser
2D keeps asset production, physics and mobile performance manageable, and it suits short shareable loops. 3D raises the ceiling on spectacle and the cost of everything else: assets, lighting, input, load size and device support. For a first launch, pick the option you can finish.
- Choose a loop that works with one thumb on a phone.
- Set a load-size budget before you add assets.
- Prefer procedural or shape-based art over asset packs you cannot license.
- Decide early whether audio is required for the loop to read.
Performance budget
- Target a steady frame rate on a mid-range phone, not a laptop.
- Cap active entities and particles; pool instead of allocating.
- Measure with the browser profiler before optimising.
- Test on a throttled connection and a cold cache.
Mobile controls and QA
- Touch targets large enough for a moving thumb.
- Prevent page scroll and pinch-zoom inside the play area.
- Test collision and input at different frame rates.
- Handle resize, rotation and backgrounded tabs.
- Watch five people play without instructions.
Browser Game Launch Kit
Milestone prompts, game structure, performance rules, mobile QA, export checklist and release process.