Ship a browser game: loading, mobile, fallbacks, hosting
From the OpenDrama Create Wiki
A prototype that plays on your machine is about half of a shipped game. The other half happens on a stranger's phone: a link opened inside a chat app, a 4G connection, a GPU a quarter as fast as yours, a thumb instead of a mouse, maybe no WebGPU. This is the release checklist we run on every AI-built browser game before the link goes out, with the number we hold each step to.
When to use it
Use it once the core loop is fun and before anyone outside your team gets the link. You're not ready yet if:
- The screen stays blank for more than a second while scripts download.
- Players wait more than ~5 seconds on 4G before they can press anything, or the first payload is over 5–10 MB.
- It only runs in desktop Chrome: the WebGPU path has no WebGL fallback, or it breaks inside the X, Instagram or WeChat in-app browsers.
- A mid-range phone holds under 30 fps, or gets slower after a few minutes.
- Touch is an afterthought: the page scrolls or zooms while you play, buttons are smaller than a fingertip.
- The shared link shows no image or title in the preview card.
- Anything loads from a CDN or another domain (fonts, three.js from a CDN, Draco decoders from Google's servers). Some hosts block that, OpenDrama's game sandbox included, and the game breaks without a clear error.
The targets we hold: something on screen in under 1 s, playable in under 5 s on 4G, 60 fps on desktop and a steady 30–60 fps on a 3–4-year-old phone, and the same game in every current browser. If you're still looking for the fun, this is too early: go back to spec-first building.
Members read on
The rest of this page is for members
- 18 more steps
- 3 reference tables
- 6 more sections
Create a free account, top up once — from $0.99 — and the whole wiki is yours.
- Every breakdown, Skill and Prompt
- New pages every day
- Prompts copy in one tap
See also
Breakdowns that use this
More in AI games
View all →An anti-gravity racer in two days: three cups, online lobbies, cars made by players' AI
Stefan rebuilt his childhood favourite, F-Zero X, as the browser racer ZERO-G with AI in two days, and it was played 1,000+ times. Here's the asset pipeline and the design that makes people finish a race.
Day 20 of an AI-built strategy game: a stone golem that wakes up, and a tavern
Stefan is building the strategy game he has wanted for 15 years with AI. Day 20 adds a golem that hides as a pile of rocks and a tavern where you hire fighters. We follow the golem from reference images into Unity.
Desk photos to a playable kart racer: Gemini 4 Argon, Blender MCP and Three.js
genevieve__h from Google AI Studio turned photos of her home-office desk into a kart racing game with Gemini 4 Argon, Blender MCP and Three.js. We rebuild the method frame by frame.
One person, 16 days, Opus 5.5: The Little Prince as an explorable 3D game
Sac built a planet-by-planet 3D Little Prince with Opus 5.5, Tripo and Blender, playable in the browser. Here's the asset pipeline and how the scenes are organised.
After going viral: how Sky Reach added a Ring world and multiplayer rooms
Tesana says a user's space game, made with a few prompts, went from 2.5M to over 3M views in just over a week. Here's how it added a Ring world and multiplayer without breaking what already worked.
Lyrio: a 3D exploration game built on movement, made with Opus 5.5 and Three.js
A fox-eared scout runs, launches off Wind Springs and glides between floating islands. We break down how the movement set becomes the whole game, and how the collectibles feed it.
