Pass the first-screen checks
Start from a fresh visit or install. Confirm that instructions and the first action fit on screen, the game begins without accidental browser zoom or scroll, and the player can identify the goal before moving. If it is a web game, verify the viewport is set for mobile and check with browser controls visible. If it is native, check safe areas and launch behavior separately.
Use this short check list and write down pass or fail:
- The first goal and primary action are visible without horizontal scrolling.
- A first-time player can start and pause using the intended touch action.
- No essential instruction is hidden by browser controls, a notch, or system UI.
- An interrupted run resumes or resets according to the stated game rule.
Test a complete round with touch
Play from start to win or loss. Tap each control near its visible edge, try the primary action repeatedly, hold it if holding is allowed, and touch outside the play surface. Check that a canceled gesture clears any held state. MDN’s touch guide documents start, move, end, and cancel events; the game should define what the player sees for each supported gesture.
Interrupt, resume, and retest
Switch away during play, lock and unlock the phone, then return. Verify the chosen timer rule, audio state, and current run state. Rotate once if the game supports rotation. Restart, then confirm score, level, and controls return to the intended starting values. For an Android or iOS app, repeat the same scenario on the release candidate; for a hosted browser build, repeat after a reload. Use the same steps after each fix so comparisons stay meaningful.
For an Oneshotgems prototype, use Playtest for the check and record a specific failed step in Chat. Ask for one correction, then repeat that step and a complete round on the new version.
Questions about mobile game prototype checklist
How many phones should pass before adding content?
Start with one representative physical phone and the narrowest viewport you support, then add devices based on audience and known platform differences. Passing two cases does not prove every device will behave the same.
Can responsive design emulation replace phone testing?
No. Emulation helps compare viewport sizes, but real touch, system gestures, audio routing, and interruptions need actual device checks.