A browser game can look excellent on a desktop and still fail the moment a phone rotates, the address bar changes height, or a thumb covers the important control. Our phone check starts before the game itself.
Start with the first tap
We open every game from a normal article-like page and require a deliberate Play action. The first tap should load the game, not trigger an advertisement or a second navigation. Buttons need enough space around them to avoid accidental taps.
We then check the loading state on a normal connection and a throttled connection. If the player offers no clear feedback, it does not pass.
Change orientation more than once
Some games resize correctly on the first turn and break when the phone returns to portrait. We rotate in both directions, reopen the browser controls, and check that the play surface remains reachable.
Text must remain readable without zooming. Important buttons should not sit under the home indicator, browser chrome, or a sticky advertisement.
Finish a real round
A short smoke test misses delayed audio, memory pressure, and controls that become awkward in later levels. We finish at least one representative round, use pause and restart, and return to the surrounding page.
Passing means more than “the iframe appeared.” It means a player can start, understand, play, and leave without getting trapped.
