Turn an HTML5 request into a clear game brief

A request for HTML5 usually names a delivery goal rather than a complete technical specification. Establish which browsers, devices, screen sizes and input methods the game must support before selecting a renderer or framework.

Ask how the game is launched, whether it must work offline, what it needs to save and whether sound can begin only after a player interaction. Define measurable targets such as load size, frame-time budget and minimum text size instead of assuming the word HTML5 answers those questions.

Build a small acceptance prototype on the least capable target device. It should load an asset, play a sound after input, resize, pause and save a result. This exposes platform constraints before the full game is committed to them.

Questions for the brief

• Which device and browser versions are required?
• What is the maximum first-load transfer size?
• Does progress need to survive a reload?
• Which interaction replaces a mouse on touch devices?