Key takeaways
- A touchscreen has no tactile feedback and no fixed reference point, which is why virtual sticks feel imprecise however well they are implemented.
- Thumb occlusion is a real constraint: your hands cover part of the display, and the covered part is where controls usually sit.
- Auto-fire removes an input that adds no decision, which frees the player's attention for the input that does.
- Removing inputs is a design choice about which skill the game tests, not a simplification for its own sake.
- Fewer inputs also widens who can play, which is a benefit that costs the design nothing.
A touchscreen is bad at exactly the inputs an arcade game traditionally relies on, and good at one it barely used. Understanding which is which explains most of what separates a mobile action game that works from one that frustrates.
What a touchscreen cannot do
No tactile feedback. A physical stick or button can be located and felt without looking. A touch control cannot. Your thumb drifts off a virtual stick and you find out from the game's behaviour rather than from your hand.
No fixed reference. A physical stick returns to centre. A virtual one has whatever centre it was given, and floating implementations move it. Neither solves the problem: you cannot feel where neutral is.
No reliable pressure or partial input. Analogue nuance that a physical stick provides is approximated at best.
Together these are why virtual joysticks feel imprecise however carefully they are implemented. It is a property of the input surface, not of the implementation.
Thumb occlusion
The second structural constraint, and the one designers underestimate.
Your hands cover part of the display while you play. On a phone held in two hands, the lower corners are obscured — and those corners are where controls conventionally sit, so the controls obscure the area immediately around themselves.
That matters because the area near your controls is often where you need to see. A hazard approaching from the bottom left is hidden by the hand controlling movement.
Three responses designers use:
- Move the action away from the covered region, keeping important information centred and high.
- Reduce the number of controls, so less of the screen is occupied.
- Use the whole screen as the control, so there is no fixed control region to obscure.
What auto-fire actually solves
Auto-fire is often described as a simplification. It is more precisely the removal of an input that carries no decision.
Ask: does holding fire involve a choice? In most shooters, firing constantly is always correct. There is no situation where you want to stop. So requiring the player to hold a button adds effort without adding a decision, and it occupies a thumb and a portion of attention.
Remove it, and both are freed for positioning — which is a decision, continuously.
The general principle: an input that never involves a choice is overhead. Removing it does not reduce depth, it relocates attention to where the depth actually is.
Removing inputs is a design decision
This is the part worth stating clearly, because "simpler controls" sounds like a concession and usually is not.
A shooter with auto-fire is testing positioning. A shooter requiring manual fire and aiming is testing positioning and input management. Those are different games with different skills, and neither is a lesser version of the other.
The most extreme version removes aiming entirely. What remains is movement — and a game where movement is the only input is a game entirely about reading the field and choosing where to be. That is a legitimate and demanding design, not a stripped-down one.
Control schemes and what each tests
| Scheme | Inputs | What it tests |
|---|---|---|
| Virtual stick + fire button | Two thumbs, two functions | Positioning plus input management |
| Auto-fire + virtual stick | Two thumbs, one function | Positioning, resource timing |
| Drag-to-move, auto-fire | One thumb | Positioning only |
| Tap-to-move | Intermittent | Planning over reaction |
Moving down the table, the game becomes more about spatial reasoning and less about manual dexterity. Which is better depends entirely on which game you wanted to make.
The accessibility dividend
Fewer simultaneous inputs, larger touch targets and no requirement for precise timing all widen who can play.
This is a real benefit that costs the design nothing when the removed inputs were not the skill being tested. Guidance on target sizes and on not requiring precise timing appears in accessibility standards for interfaces generally — WCAG is the web equivalent, and its reasoning about pointer targets and timing transfers directly to games.
The practical version for a player: if a game's controls are fighting you, that is often a design problem rather than a skill problem, and a game with a scheme suited to your hands will not be a lesser game.
Where our games fit
Zombie Survival: Last Survivor takes the most reduced position on the table above: weapons fire automatically and movement is the entire input. That makes the game about reading the field and choosing where to be — and it makes mid-run upgrade choices, covered in power-ups and build design, the other half of the decision-making.
Space Shooter - Galaxy Arcade sits further up: four distinct abilities — main weapons, a secondary attack, a charged Ultimate and a Shield — so resource timing is an explicit skill alongside positioning.
Both are free to download on Google Play, supported by ads, with optional in-app purchases and Everyone content ratings.
Horde survival versus wave shooter covers how the two structures differ, offline arcade games for Android covers what works without a connection, and battery and performance in mobile games covers the other constraint phones impose. Everything we make here is under action and arcade games.
Good to know
Frequently asked questions
Why do virtual joysticks feel imprecise?
What is thumb occlusion?
What does auto-fire solve?
Is removing inputs just simplification?
Does simpler control help accessibility?
Sources
- Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)World Wide Web Consortium (W3C) — accessed
- Space Invaders (opens in a new tab)The Strong National Museum of Play — accessed
