Check that the on-screen buttons for a phone are big enough to hit

Buttons that look fine in the game's own small picture can be tiny once the game is scaled to a phone, overlap the neighbour or sit half off the screen. This entry measures them the way a thumb meets them and lists every button that will frustrate players.

Why this works

A finger is big and blunt, and its size does not change with your game's picture. So a button must be judged by how large it ends up on the real screen, with space around it, not by how it looks in the small drawing you made.

When not to use it

Skip on-screen buttons altogether when a tap or a swipe anywhere can do the job, such as a one-touch game. Fewer targets means fewer misses. Also skip it for games meant for a keyboard or a controller only.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• 25 lines of example code with 4 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Check that the on-screen buttons for a phone are big enough to hit" (read_entry action-touch-buttons-size-overlap) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP