By Greg Nowak. Updated 4 November 2026.
A browser game can be easy to share and surprisingly demanding to maintain. Before commissioning one, it helps to ask what must happen while someone plays, what can be prepared beforehand, and what the business needs to keep afterwards.
KotobaMon provides a practical example. Players explore a 3D island and answer Japanese vocabulary questions to help catch monsters. The game uses native JavaScript modules, a local copy of Three.js and prerecorded Japanese speech. It runs as static files, with progress saved in the browser. Those choices suit a contained experience; they also establish clear limits for anyone planning something similar.
Start with the interaction people came for
In KotobaMon, answering a vocabulary question improves the chance of a capture. Japanese text, romaji and English accompany the spoken lines. The project case study describes how the learning mechanic fits into play.
For a client project, define that central interaction before discussing frameworks. What should a visitor understand or accomplish in their first few minutes? A training experience might need someone to practise a decision. A product demonstration might need them to explore a feature.
Agree on observable acceptance criteria: a new user can begin without guidance, understand the feedback and complete the intended task. Test that early, on the devices your audience actually uses. Extra levels and polished effects can follow once the interaction earns them.
Which requirements change the architecture?
Use this matrix when scoping an interactive campaign, learning tool or agency prototype. The right-hand column identifies requirements worth pricing before development starts.
| Decision | A simpler option fits when… | Plan additional work when… |
|---|---|---|
| JavaScript delivery | Dependencies are few and manageable as native modules. | TypeScript, many packages or asset processing justify build tools. |
| Voice | The script is fixed and clips can be approved beforehand. | Speech must respond to individual users or changing text. |
| Progress | A save belongs to one browser and losing it is tolerable. | Users need recovery, device sync or verified completion records. |
| Artwork | Simple shapes support the intended visual style. | The brief requires detailed models or complex animation. |
No build step still means managing dependencies
KotobaMon serves its JavaScript directly, without bundling or transpilation. Its code-built terrain and characters also keep the artwork workflow small.
The current Three.js installation guide documents a route without build tools, while recommending npm and a build tool for most users. For native modules, keep Three.js core and add-ons on matching versions, record the version supplied, and maintain an import map when imports use package names such as three.
Develop through a local web server. With Node.js installed, run npx serve . from the project directory and open the address it prints. Double-clicking an HTML file can break features because browsers treat local files differently.
A build tool can become worthwhile as dependencies grow. It can also produce ordinary static files for deployment: choosing static hosting does not require giving up a build pipeline. Base that decision on the team's workflow and maintenance needs.
Self-hosted voice: generate, review, publish
KotobaMon's Japanese voice lines were generated with self-hosted Kokoro and saved as audio files. The player downloads those files; playing a line does not request fresh speech generation.
That distinction matters when estimating operating costs. Fixed narration avoids a speech-generation charge for each play, but still requires hosting, bandwidth and editorial work. Personalised dialogue introduces a different runtime service requirement.
The Kokoro-82M model card identifies the weights as Apache-2.0 licensed. Record the exact model, voice, software versions and applicable licence notices in the handover. Keep the script, subtitle text and generation settings together so a future editor can reproduce a clip.
For language learning, have a qualified speaker review pronunciation and meaning. Approve the audio alongside its subtitles, then version both together. Also make the experience understandable with sound muted and provide clear playback controls.
Decide what a lost save would cost
Browser storage removes the need for an account, but it is not a recovery service. As MDN explains, localStorage persists across normal browser sessions, while private-session data is cleared when the last private tab closes. Browser policy can also prevent storage.
Handle reads and writes defensively, and tell the player when saving fails. Version the save format so an update can recognise older data. Explain that clearing browser data can remove progress and that saves do not automatically follow users to another device.
For a casual game, that may be acceptable. For business training records, agree on authentication, server-side storage, recovery and reporting before launch. A local score alone cannot establish who completed training.
Give static deployment a proper release routine
Static hosting reduces the services you operate, but releases still need coordination. A returning browser must receive compatible HTML, modules, styles and audio references.
Following MDN's caching guidance, use new URLs for changed assets. Configure HTML with Cache-Control: no-cache so it revalidates. Assets whose contents never change at that URL can use Cache-Control: max-age=31536000, immutable. Publish assets before switching the HTML, and retain the previous release for rollback.
If using version query strings, update every relevant import and confirm the CDN includes those parameters in its cache key. Changing only the entry module's URL does not version its dependencies.
Before signing off, test fresh and returning sessions, keyboard and touch controls, audio playback, and saving across reloads. Check performance on a representative phone. Give the next maintainer deployment instructions, dependency versions and a named owner for future updates.
Scope the smallest complete experience
This approach is worth considering when content is mostly fixed and the brief needs a convincing interaction without accounts or shared records. Let the requirements determine where simplicity ends.
If you are commissioning an interactive web project, bring Greg the intended audience, core interaction, target devices and reporting needs. Discuss the scope and delivery choices with Greg, or play KotobaMon to explore the example.
Related on GrN.dk
- Google Review Link Generators: What Small Teams Actually Need
- SEO in 2026: What Actually Changed Since 2024
- AI automations need a spend dashboard before the first runaway bill
Need help with this kind of work?
Discuss your interactive web project with Greg Get in touch with Greg.