Skill Game Dev →

Touch Controls Thumb Zones

Mobile touch controls design + implementation thumb-reachable zones (5.5"-6.7" screens)…

Build ergonomic, accessible touch controls for mobile games: thumb-reachable zone mapping, virtual joystick and action-button placement, tap/hold/swipe gesture disambiguation, and platform-specific haptic feedback. It grounds layout in Fitts's Law and Steven Hoober's thumb heatmap so buttons land where the thumb naturally rests, and it uses the event-driven Input System instead of per-frame polling so input stays under one frame of latency.

$15 one-time
Add to a kit →

Prices include 20% VAT. · Forged on real agency work · one-time, no lock-in

  • Type Skill
  • Category Game Dev
  • Delivery Email · instant
  • License One-time
Run preview
forgehouse, touch-controls-thumb-zones

Inside the run · no black box

See the actual work before you buy it.

Where does a thumb actually rest on a 6.7 inch screen? Every layout decision here starts from that heatmap and ends in measured latency, gesture thresholds and restrained haptics:

  1. Lays out controls on the Hoober thumb heatmap: joystick at normalized (0.15, 0.20) bottom-left, primary action at (0.85, 0.22) where the right thumb naturally rests, pause and minimap pushed to the top where the thumb never blocks them. Every button is enforced at minimum 44pt on iOS and 48dp on Android per Fitts's Law, and a left-handed mode mirrors the whole config on the X axis.
  2. Wires input through the Unity Input System with EnhancedTouch in event-driven mode: zero-allocation callbacks instead of polling Input.touches every frame, targeting under 16ms tap-to-action latency, one frame at 60fps.
  3. Runs gesture disambiguation as a priority queue with hard thresholds: swipe resolves first (over 50px movement under 300ms), then hold (over 400ms with under 15px drift), then tap as the least restrictive fallback (under 150ms, under 10px). One touch sequence can never fire two gestures.
  4. Adds haptics only on 3 to 4 critical events (button confirm, damage taken, item collected, error) through a platform abstraction over CoreHaptics on iOS and VibrationEffect waveforms on Android. Haptics on movement or menu navigation are banned because habituation kills the signal.
  5. Hardens the edges: Screen.safeArea syncing so no button hides under a notch or Dynamic Island, a 1.5 second hold-to-confirm bar on IAP and destructive actions as gesture-injection protection, and accessibility labels on every critical element for VoiceOver and TalkBack.
  6. Verifies with the checklist: button sizes measured in Inspector, gesture thresholds tested, haptics confirmed on both platforms, no legacy Input.touches left in the codebase (grep check), and input cost under 1ms in the Profiler.
Use cases · what happens when you plug it in

One power source. 6 lines out.

touch-controls-thumb-zones · core

core active · 6 lines

  1. First-time setup of a virtual joystick plus action buttons

    ✓ first-time setup of a vi…
  2. Fixing a 'controls feel slippery' complaint caused by wrong thumb zones

    ✓ fixing a 'controls feel
  3. Resolving a gesture conflict where tap and swipe fire together or vanish

    ✓ resolving a gesture conf…
  4. Adding one-hand vs two-hand and left-handed accessibility modes

    ✓ adding one-hand vs two-h…
  5. Adding distinct haptic patterns for hit, collect and error events

    ✓ adding distinct haptic p…
  6. Wiring VoiceOver/TalkBack labels onto critical UI elements

    ✓ wiring voiceover/talkbac…
Benefits · what you walk away with

Yours to keep.

Drag time forward. Watch what stays.

Forever

That's what owning means.

The rented stack

ai writing tool: subscription

expired · access lost

analytics suite: subscription

expired · access lost

design platform: subscription

expired · access lost

(nothing left)

Your forge

  1. Turn 'controls feel slippery' one-star reviews into ergonomic, reachable layouts

    license: perpetual
  2. Keep input under one frame of latency with event-driven, zero-alloc handling

    license: perpetual
  3. Stop tap-and-swipe conflicts with a priority-based gesture arbiter

    license: perpetual
  4. Pass App Store accessibility review with VoiceOver/TalkBack support

    license: perpetual

subscriptions expire · deeds don't

What's included · the full manifest

Everything in the box.

Pick a piece up. Watch it work.

A thumb-zone layout helper with right-handed and mirrored left-handed configs

part 01 of 06 · in the box

6 parts · one working system · ships instantly by email

Who it's for

This wasn't forged for everyone.

  • Not for you if you'd rather rent a tool than own one.
  • Not for you if you want someone else to run your stack.
  • Not for you if you're happy guessing.
Still here? Good.

Mobile game developers building or fixing touch controls who need ergonomic thumb zones, clean gesture handling and accessibility.

then this was forged for you.

Works with

Universal by design: these run in any AI. Delivered in the open Agent Skills + MCP format (native in Claude); ChatGPT, Gemini, Cursor and Copilot adapt the same files their own way.

  • Claude Native format
  • ChatGPT Adapts via open standards
  • Gemini Adapts via open standards
  • Cursor Adapts via open standards
  • Copilot Adapts via open standards
Questions · still in the air

Catch what's on your mind.

the air is clear. nothing between you and the forge.
catch a spark: the forge will answer

  1. Is this Unity-specific, or can I use it in any mobile engine?

    The implementation layer is Unity: it builds on the event-driven Input System with EnhancedTouch and ships C#-style handlers, plus iOS CoreHaptics and Android VibrationEffect integration. The ergonomic layer: Fitts's Law sizing and Steven Hoober's thumb heatmap, applies to any engine, but you would reimplement the code.

  2. What actually fixes a 'controls feel slippery' complaint?

    Usually it is placement, not code: buttons sitting outside the natural thumb-rest zones on 5.5 to 6.7 inch screens. The layout helper repositions controls along the thumb heatmap, and the event-driven handler keeps input under one frame of latency with zero per-frame allocation, so taps register where and when the player expects.

  3. Does it cover gamepad, keyboard or stylus input too?

    No. The scope is touch: thumb zones, virtual joysticks, tap/hold/swipe disambiguation, multi-touch, haptics and VoiceOver/TalkBack accessibility. Physical controllers and pointer hardware need a separate input setup.

  4. How is it delivered?

    By email right after purchase: ready to run, downloaded instantly, no setup wait.

  5. One-time or subscription?

    A one-time purchase; no subscription or hidden fees. VAT (20%) is included.

  6. Can I get a refund?

    As a digital product, it can’t be refunded once downloaded. That’s why we show exactly what’s inside and who it’s for, right here.