Starting From the Complaints
When readers tell us a game "controls badly", they are almost never able to say why, and that is reasonable — input is felt rather than analysed. Part of our job is to turn the feeling into a specific fault, because a specific fault can be described, compared between games and, occasionally, fixed in an update.
Over a long run of testing at The Weekly Report, the complaints resolve into a short list. Six failures cover the great majority of what makes a touchscreen game unpleasant to hold. Here they are in the order we tend to encounter them.
1. The Ported Layout
The most common failure is not a design decision at all. It is the absence of one. A game built first for a controller or a keyboard gets a touch layout by drawing the original buttons on the glass, in roughly the arrangement they occupied on the physical device.
The result never works, because the two input surfaces have opposite constraints. A controller's buttons are felt, not seen, and the hands do not cover the display. Painted buttons must be seen to be hit, and the hands covering them are the same hands that must watch the screen. A layout that was efficient in plastic becomes a set of targets the player has to look away from the action to find.
2. The Anchored Stick
A virtual directional stick drawn at a fixed point on the screen assumes the thumb will return to that point. It will not. The hand shifts, the grip changes, and after thirty seconds of play the thumb is a centimetre from where the stick is drawn — still pressing, still generating input, but with no idea which direction is which.
The remedy is well established and still not universal: let the stick appear wherever the thumb makes contact and recentre it on every new touch. Movement then becomes relative to the player's hand rather than to a coordinate the designer chose. The difference in feel is dramatic and the implementation cost is small.
3. Controls Sitting on Top of the Action
Because a hand is opaque, whatever is behind it is gone. A scheme that places its controls over the region where important things happen has traded away visibility for convenience, usually without noticing.
We test this by playing with the screen recorded and then watching the recording, which shows what the game intended to display. When the recording contains information the player could not possibly have seen, the layout is at fault. The most frequent offenders are a health or resource bar pinned to the bottom edge and enemies that enter from the lower corners.
4. Targets the Size They Look
A drawn button and its touch target are separate things. When they are identical, every input landing a millimetre outside the visible edge does nothing, and the game feels unresponsive even though it is behaving exactly as specified.
Generous invisible margins around every interactive element remove an entire class of frustration and are invisible to the player in the best sense — they never know it happened. The same idea applies in time as well as space. A small window of tolerance on either side of a timed input absorbs both touchscreen latency and a phone being held in a shaking hand.
5. Gesture Vocabularies That Are Too Large
Gestures are the natural language of the touchscreen, and they can be pushed too far. Once a game distinguishes a swipe from a long swipe, a double tap from a tap-and-hold, and a two-finger pinch from a two-finger rotate, it is asking the player to produce distinctions the hand cannot make reliably — particularly one-handed.
Our rule of thumb: a mobile control scheme can support a handful of gestures that are qualitatively different from one another. It cannot support several that differ only in degree. When a game misreads an input, the player has no way to know what they did wrong, and unlike a missed button press there is no visible target to blame.
6. Right-Handed by Default and by Assumption
A fixed layout designed around a right thumb is unusable for a meaningful group of players and awkward for anyone whose other hand is occupied. Mirroring is trivial to implement and is missing far more often than it should be. We treat the presence of a mirror option, or of freely repositionable controls, as a genuine mark in a game's favour rather than a nicety.
A Comparison We Keep Coming Back To
| Scheme | Strength | Weakness | Best suited to |
|---|---|---|---|
| Floating virtual stick | Continuous, precise movement | Occludes a corner; needs practice | Open-space action and exploration |
| Fixed virtual stick | Predictable position | Thumb drifts off it during play | Games played on a flat surface |
| Swipe and tap | No permanent overlay; clean view | Low precision, poor discoverability | Puzzles, runners, card and turn-based play |
| Contextual single button | Playable one-handed anywhere | Removes fine control from the player | Short-session and one-handed games |
| Drag-to-aim | Precision without occluding the target | Slow; unsuited to real-time pressure | Aiming, planning and strategy layers |
| Motion and tilt | Novel, hands stay clear of the screen | Unusable in a moving vehicle | Nothing, as a sole scheme |
The table is not a ranking. It is a set of fits, and most of our criticism of control schemes amounts to a mismatch between the scheme and the game rather than a scheme being bad in itself.
How This Reaches the Score
We play each game one-handed, then two-handed, then left-handed, and we hold the device deliberately badly at least once. The failures above are noted individually rather than folded into a single verdict of "clunky", because a reader deciding whether to try something deserves to know whether the problem is a fixed stick they will adapt to or an occlusion issue they will not.
Controls carry real weight in our overall figure, which is our own editorial judgement and is not the store's star average. The weighting is documented in our methodology, the standings are on the ranking, and the desk behind the testing is described on our about page.