How We Hand-Review Browser Games

Published November 10, 2026 · BooBoo Editorial Team

Where this standard stands: this page is the standard we now publish and review against. Reviews published before November 2026 were written under earlier, less formal notes — they are being brought up to this standard page by page, and each one states what its session actually covered. If a review page makes a claim this standard would not support, that page is wrong, and we would rather narrow the claim than defend it.

A useful review tells you what happened

A browser game can run through several different distributors and builds. A review of one version is not automatically a review of every version with the same title. Our review records therefore start with the exact game URL, the distributor or embed source, and a dated test session.

A reader should be able to distinguish three things: what the game's publisher says, what our reviewer directly observed, and what has not been checked. If a reviewer reached a menu but did not finish a level, the review says so. "Launched in our desktop browser" is useful information; "fully tested on every device" is a much larger claim — one we do not make without device logs.

What each test record contains

Build and source. The BooBoo game URL and the visible partner or embed source. If the title is a clone, adaptation, or fan project, we do not imply it is the official original. If the source cannot be established, it stays unknown — we do not invent developers.

Device and input. Browser, operating-system family, viewport or device, and input used. A mouse drag on a desktop does not verify touch input on a phone, and a narrow browser window is not a real mobile device.

Scope. The actual actions: opening the player, reaching the title, following a tutorial, making a legal move, completing a level, testing a reset. Each action has a result. An attempted move with no confirmed outcome stays an attempted move.

Limits. What remains unknown: later levels, saved progress after closing the tab, touch controls, account requirements, or long-session interruptions. A short session never becomes a claim about the whole game.

Before a page may say “hand-reviewed”

  1. The title, instructions, and playable embed match the same build.
  2. The game started and at least one meaningful core action was demonstrated, with a recorded outcome.
  3. The relevant restart or retry path was checked, or the record explicitly says it was not verified.
  4. Any consent screen or advertising interruption encountered is documented, without clicking advertisements.
  5. Tested input, session date, and untested items appear in visible text on the page.
  6. A separate accuracy pass confirms the article does not exceed its evidence.

This is a publication gate, not a demand for a particular score or word count. A concise guide with one verified action and clear limits is more useful than a long article of generic controls.

Menus, privacy choices, and ads are separate observations

A consent screen tells you what choices were displayed. It does not prove which network requests were sent or whether a service complied with privacy law. Likewise, a skippable advertisement in one session does not prove every player sees the same advertisement or timing. Network or privacy-compliance claims require a separate, appropriately authorized review — we do not make them from a gameplay session.

Screenshots, sources, and ownership

Screenshots carry captions describing the actual scene and the correct distributor. External player ratings may be quoted visibly with their source and verification date; they are never presented as ratings collected by BooBoo, and never placed into structured-data rating fields to chase search stars.

Dates and corrections

A game's release date, a reviewer's test date, and a page's substantive-update date are three different facts, and our pages keep them separate. Rebuilding the site does not make an old review look newly tested. If evidence no longer supports a page, the first response is to narrow the claim, re-test, or merge the page — not to generate another near-identical article.

Found something our own standard would not support? Tell us via the contact page.

Review approvals and corrections are owned by the BooBoo Editorial Team (organization attribution; we do not publish invented editor personas). Evidence records are retained with their session dates.