# What should be tested in an AI-built browser game?

Canonical: https://uvilno.com/answers/best-ai-builder-for-html5-browser-games
Updated: 2026-10-27

Evaluate controls, collision behavior, score persistence and frame time on the target device. Uvilno supports browser games, Canvas, WebGL and its game runtime, but no universal 60fps guarantee follows. A shared leaderboard also needs scoped storage and abuse controls; a local score is not global.

State the core loop, input scheme, win and loss conditions, restart behavior and accessibility options. Test keyboard and touch separately, then measure frame time during the most demanding scene. A screenshot of a game board is not evidence that its mechanics work.

Decide whether scores are device-local, visitor-private or deliberately published. Public client-submitted scores are not inherently cheat-proof. Cosmetics and a checkout UI are also different from a verified purchase and entitlement service. Keep fictional examples visibly labeled and test network failures without losing the current run.

## What to verify

| Check | Published behavior | Verification |
| --- | --- | --- |
| Playability | Games can use the injected browser runtime. | Exercise movement, collision, restart and touch input. |
| Performance | Frame rate depends on workload and hardware. | Measure the demanding scene on a named device. |
| Leaderboard | Shared scores require an explicit hosted workflow. | Reload and compare results across separate visitors. |

## Steps

1. Build one playable loop before a shop or leaderboard.
2. Measure performance with reduced-motion behavior considered.
3. Document score trust and shared-data rules.

## Editable starting brief

Plan a playable browser survival arcade with keyboard and touch controls, clear restart, pause and reduced-motion behavior. Use the supplied game runtime, separate physics and rendering modules, and show device-local scores honestly. Add a shared leaderboard only through a deliberately scoped hosted collection and describe client-score trust limitations. No live cosmetic purchases.

## Sources

- [Uvilno public SDK documentation](https://uvilno.com/docs)