What’s the smallest a tap target can be before it gets frustrating to hit?

A tap target gets frustrating below roughly forty-four to forty-eight points on a side, with adequate spacing between neighbors, because a real finger is imprecise and needs both area to land on and room to miss the wrong thing. Apple’s Human Interface Guidelines call for a minimum of about 44 by 44 points, and Google’s Material Design recommends about 48 by 48 density-independent pixels, so that range is the working floor most platforms converge on. Treat it as the comfortable, reliable-hitting size, not the smallest thing that still looks clean. Crowding and undersizing both produce misses, and the goal is dependable taps, not a tidy interface.

The floor exists because a fingertip contacts the screen across a blurry patch several millimeters wide, far larger and far less exact than a cursor, and the device has to guess your intended point from that smear. Give it a target near the platform minimum and the guess is easy. Shrink the control to look elegant and you force the user to aim, which on a phone in motion, one-handed, with a thumb, means repeated near-misses and the small rage of tapping twice. The point is not that smaller targets are impossible to hit, it is that they convert a reflexive action into a careful one, and careful is exactly what a fast mobile interaction should not require.

Spacing matters as much as size, and accessibility guidance makes that explicit. WCAG’s Level AAA target-size criterion (2.5.5) asks for at least 44 by 44 CSS pixels, while the broader Level AA criterion (2.5.8) sets a smaller absolute floor of 24 by 24 CSS pixels but lets a target stay small only if it has at least 24 CSS pixels of clear space around it. The practical reading is that area and gap trade against each other: a control near the lower bound needs generous separation from its neighbors, because two correctly sized buttons jammed edge to edge still produce mis-taps when an imprecise finger lands on the seam. A row of icons proves it daily, each glyph may be drawn small, but if the tappable region and the spacing around it meet the floor, the row feels reliable, and if they do not, it feels like a minefield.

Note one exception: pure inline text links inside a paragraph are exempt from the strict spacing rule, since line height constrains them and forcing huge gaps would wreck the prose, and that decorative or duplicated controls with an equivalent large target nearby can be smaller without harm. So the floor governs standalone, primary tap targets, the buttons and controls a user must hit to proceed, more than every clickable pixel on the page. The figures above are a working guide to verify against the current platform and accessibility documentation, not a number to invent from memory.

Size your real controls to land in that forty-four to forty-eight range, give every standalone target at least the spacing the accessibility floor asks for, and test the result with an actual thumb rather than a mouse on a wide monitor. Build for the imprecise finger, not the tightest tidy layout, and the taps will land the first time.