Phone or computer? How to plan your video game controls

Nov 20, 2026|5 Min

Unity Team - Unity Technologies

The same game scene shown on a phone with touch controls and on a laptop with a keyboard and mouse, with an optional controller below, all around an orange character leaping onto a floating platform. Image generated by Claude Sonnet 5.5, November 12, 2026.

Choose your input devices before you build, and you shape what players can do and how comfortable they feel doing it.

Video game controls are the inputs players use to act in your game, such as taps, key presses, and controller buttons. Picture a small robot hopping across a gap between two floating platforms. On a phone, you tap a button with your thumb. On a laptop, you press the spacebar. If you plug in a controller, you press a face button. The game is the same, but each device changes how it feels, what you can ask players to do, and how long they can play before their hands get tired.

That’s why controls matter. They’re how players talk to your game, and they set the limits of what players can do in it.

When you create a game with a tool like Unity Spark, Unity’s AI-native game creation platform, you describe your game in plain language. You don’t write input code or learn a traditional game engine, but you still make the decisions an engine normally forces on you, and controls are one of them. Your players will open your game on a phone, a desktop, or a laptop, so you’ll plan for two main setups: touch, and keyboard and mouse. A controller is an optional extra.

Work through these six steps before your first prompt, and you’ll write a clearer request and build a game that more people can enjoy.

1. Start with verbs, not buttons

List what your player does in your game: move, jump, aim, pick up, confirm. Keep it to three to five actions for your first game. Then decide which device triggers each one.

Developers who work in the Unity Engine follow the same order. The Input System separates an action, such as “Jump,” from the controls that trigger it, and it groups actions by context, such as one set for walking and another for driving. With Unity Spark, you don’t need to set any of that up yourself, but you can borrow the habit. Write “the player jumps” first, and decide later whether a tap, a spacebar press, or a button does the job.

2. Match each device to your actions

Every device is good at some things and awkward at others. Your players will most likely use one of two setups: a phone, where they touch the screen, or a computer (a desktop or laptop), where they use a keyboard and a mouse or trackpad.

On a phone, players control your game by touching the screen. Touch works best for taps, drags, and short sessions. Thumbs also cover part of the screen, so give them room. The Xbox Accessibility Guidelines suggest making each on-screen button, called a touch target, at least 15 mm square on a phone, and spacing buttons far enough apart that players don’t hit the wrong one. Leave a little empty space around each one so a slip doesn’t trigger its neighbor. Also, consider supporting both portrait (held upright) and landscape (held sideways) play, because some players mount their phones in a fixed position.

On a desktop or laptop, players use a keyboard and a mouse, or a trackpad, the touch-sensitive pad below a laptop keyboard. A keyboard gives you plenty of keys, and a mouse points precisely, which suits games with many actions or fast aiming. Keyboards also ask more of players, who must learn where each key sits, so keep your list of keys short. Some players can’t use a mouse, so offer a keyboard option for anything you ask a mouse to do. Many laptop players use a trackpad instead of a mouse, so avoid actions that demand fast, precise pointer movement.

A controller, also called a gamepad, is optional here. It’s the handheld device with thumbsticks, the two small joysticks, and buttons that console players use, and it can connect to a phone or a computer. Players need to own one and set it up first, so treat controller support as a bonus, not a requirement. If you do support one, avoid designs that need both thumbsticks, the two small joysticks, at once. According to the Xbox guidelines, even shooters can offer a single-stick option.

3. Design for two devices, and say which comes first

Decide which device matters most to your game, and write it at the top of your design brief. Unity Spark is a way to make and share games in a browser, so your players can open your game on either a phone or a computer. Design for your main device first, then check that the game works on the other one. The Game Accessibility Guidelines list support for more than one input device as a recommended feature.

Write each action once, then map it twice: one touch version and one keyboard-and-mouse version. Then look for actions that have no match on the other device. A pinch has no keyboard equivalent, and a mouse hover has no touch equivalent. The Xbox guidelines recommend making sure players can operate content without multi-point gestures, so give every pinch a simple alternative, such as a zoom button.

4. Check speed, complexity, and duration

Letting players remap buttons helps, but it doesn’t remove every barrier. The Xbox guidelines name three more things to check:

  • Speed: How fast must players press? A close-range fight that needs rapid presses excludes anyone who can’t tap quickly, no matter where the buttons sit.
  • Complexity: How many inputs must players use at once, or remember in order? A combo of several keys in a set order blocks players who can’t memorize it, even after remapping.
  • Duration: How long must players hold a control? Holding a key or a finger down to accelerate through a three-minute race tires players out on any device.

For a race, a toggle that keeps the car accelerating solves the problem. You can apply the same idea to sprinting, firing, and repeated jumping.

Unity’s guide to video game accessibility basics offers further insight into hearing, vision, motor, and cognitive needs.

5. Build in forgiveness

Players will miss, slip, and tap the wrong thing. Plan for it:

  • Act on release: Activate controls when the player lifts a finger or releases the mouse button, not when they first touch. That lets players slide away to cancel a mistake.
  • Skip the gymnastics: Avoid pinch and multi-finger gestures for core actions, or give players a simple alternative, such as a zoom button.
  • Offer simpler options: Let players choose how they perform key actions, such as firing automatically, tapping anywhere on the screen, or pressing a dedicated button.
  • Teach as you go: Show players their controls during play, and give them a safe place to practice. Both appear on the Game Accessibility Guidelines checklist.

6. Test on real devices and write down what you find

A control that feels fine in your head can feel awkward in your hand. Play your game on a phone and on a computer, and note two kinds of problems separately: accidental inputs, when the game does something you didn’t mean, and missed inputs, when it ignores something you did mean. Then change one control at a time and play again.

Your turn

Open your design brief and finish this sentence:

In my game, players use ___ on a phone and ___ on a computer to ___.

Save it near the top of your brief. That’s a controls plan for both devices, and it gives you a clearer first prompt. When you get access to Unity Spark, include your answer in that prompt, play what you get on a phone and a computer, and note the first control you’d change.

Ready to plan your game’s controls? You don’t need to be a developer. Try Unity Spark, Unity’s browser-based, AI game creation platform that lets you describe your game, refine it in a real web editor, and publish it for others to play.

Learn more about Unity Spark

*Header image note: The same game scene shown on a phone with touch controls and on a laptop with a keyboard and mouse, with an optional controller below, all around an orange character leaping onto a floating platform. Image generated by Claude Sonnet 5.5, November 12, 2026.