Touch Controls and Haptics for Mobile Games (2026)

Q: What is the best control scheme for a mobile game?

The one the player can see or is taught in the first 30 seconds. Start from direct touch, where players tap or drag the game objects themselves, and add virtual buttons or a stick only when the design cannot work without them. Avoid mixing visible buttons with hidden gestures. PawScooty shipped that mix first, and a tester finished Level 1 with 42 of 60 coins without changing lanes on purpose.

Q: How do I make swipe controls feel responsive?

Act when the finger crosses a distance threshold, not when it lifts. Waiting for release adds the whole duration of the swipe to your input delay. Then queue one or two follow-up inputs so a quick double swipe lands as two moves, drop inputs that are impossible in the current state, track fingers by ID so alternating thumbs work, and treat a cancelled touch as if nothing happened.

Q: What swipe distance threshold should I use?

Set it in physical distance, not pixels. PawScooty uses 40 screen pixels, which by simple arithmetic is about 2.2 mm on a 460 ppi phone and about 6.4 mm on a 160 dpi screen, so the same gesture needs three times the travel. Convert millimetres to pixels with Screen.dpi, keep a fallback because Unity says dpi can return 0, start near 4 mm and tune with real players.

Q: Should a virtual joystick be fixed or floating?

Floating, in most cases. A fixed stick asks the player to find a spot on glass that they cannot feel, so the thumb drifts off it. A floating stick uses the touch-down point as its centre, so every press starts at neutral. Add a dead zone so a resting thumb does not move the character, a maximum radius after which the base follows the thumb, and an input curve for fine control.

Q: When should a mobile game use haptic feedback?

On events that are rare and meaningful. Apple's guidance says to avoid overusing haptics because a pattern that feels right occasionally becomes tiresome when it plays often, and to make haptics optional. PawScooty had to ship version 1.0.2 because vibration was wired to six events and five of them repeat during normal play. It now fires only on obstacle contact and respects a settings toggle.

Q: How long should a haptic effect last?

For a crisp tap, very short. Android's haptics design principles say a clear effect should last between 10 and 20 milliseconds, and note that the actuator may keep ringing for another 20 to 50 ms after the signal ends. The same page advises against legacy one-shot vibrations for feedback because they can feel buzzy. Longer patterns suit sustained events, but they dilute meaning if they are used often.

Q: How do I trigger haptics in Unity and Godot?

Unity's built-in call is Handheld.Vibrate, and its documentation says the duration is decided by the operating system, so you get one fixed buzz with no strength control. Finer effects need a native plugin for Core Haptics on iOS or Android's VibrationEffect APIs. Godot offers Input.vibrate_handheld with a duration in milliseconds and an amplitude from 0.0 to 1.0, and on Android it needs the VIBRATE permission enabled.

Q: How do I stop iPhone system gestures interrupting my game?

Keep controls inside the safe area first, away from the Home indicator. Then, for edges your gameplay uses, defer the system gesture. UIKit exposes this as preferredScreenEdgesDeferringSystemGestures, and Unity's iOS Player settings include an option called Defer system gestures on edges, which makes the player swipe twice to trigger the system action. Use it only on the edges you need.

Satyam Kumar

Back to Blog

architecture

Touch Controls and Haptics Done Right: Swipes, Sticks and Buzz Budgets (2026)

By Satyam KumarNovember 15, 202613 min read

touch controls mobile game controls swipe detection virtual joystick floating joystick joystick dead zone input buffering haptic feedback core haptics android haptics handheld vibrate unity touch input godot touch input on-screen controls swipe threshold one-finger controls game feel pawscooty mobile game design

Touch Controls and Haptics Done Right: Swipes, Sticks and Buzz Budgets (2026)

Frequently Asked Questions

Share this article

Twitter LinkedIn WhatsApp

Satyam Kumar

Founder & AI Architect, AppScale LLP

AI & Cloud Architect. Helping teams build systems that scale to millions.

LinkedIn GitHub

Touch Controls and Haptics Done Right: Swipes, Sticks and Buzz Budgets (2026)

Frequently Asked Questions

Share this article

Comments

Leave a comment