Sunday Arcade guide

Our phone browser-game test checklist

The checks required before Sunday Arcade marks touch targets, orientation, loading, sound, and mobile play as independently verified.

Our phone browser-game test checklist guide illustration

A browser game can look excellent on a desktop and still fail when a phone rotates, the address bar changes height, or a thumb covers an important control. This is the checklist a reviewer must complete before Sunday Arcade marks a game as independently tested. A working iframe alone does not pass.

Start with the first tap

The reviewer opens the game from its normal listing page and confirms that a deliberate Play action loads the intended third-party player. The record notes redirects, unexpected advertising, loading feedback, and whether the main controls can be reached without accidental taps.

The loading state is checked on a normal connection and, where practical, a throttled connection. A missing or misleading status is recorded instead of being silently treated as a pass.

Change orientation more than once

The reviewer rotates in both directions, reopens the browser controls, and checks whether the play surface remains reachable. The tested phone, browser, orientation, and date belong in the game record.

Text readability, zoom behavior, fullscreen behavior, and controls near browser chrome or the home indicator are recorded as observations, not inferred from provider metadata.

Finish a real round

The reviewer completes at least one representative round or level when the game permits it, then tries pause, restart, sound, and return-to-page behavior. If a round cannot be completed, the record must say why.

Only a recorded check can change a listing from review to independently verified. Until that happens, Sunday Arcade labels the page as pending, excludes it from the sitemap, and avoids game-specific control, duration, difficulty, and compatibility claims.

Sources

Put it into practice

Related games