Platformer Games for Mobile / Touch

About This Combination

Browser platformers live or die on input latency. Anything above 80ms of keyboard lag — common on older Android WebView implementations — turns a crisp jump arc into a slot-machine. The sites that compress their physics loops properly (Nitrome has done this reliably since 2007) feel almost indistinguishable from native. The rest are frustrating and unfairly blamed on the player. Bramwell uses a USB keyboard on a Chromebook as his minimum-spec device for this genre specifically.

Device Notes for Mobile / Touch

Mobile touch is where browser games face their most hostile environment and their largest audience simultaneously. A 375px wide viewport, no hover state, variable touch latency (15ms on a Pixel 8, 65ms on a budget Android), and a browser chrome that eats screen real estate. Games that work well here have been designed for it from the start — not ported from desktop. Bramwell tests on three devices: iPhone SE (small screen), Samsung A54 (mid-range Android), and iPad Air (tablet touch). A game that passes all three is genuinely cross-device.

Compatibility

iOS Safari 16.4+ handles most WebGL. Android Chrome 110+. Firefox on iOS uses WebKit and behaves identically to Safari.

Screen Notes

Minimum 320px. Avoid games requiring hover states. Virtual joysticks add ~40ms latency on most implementations.