Mobile Task Taps Count

Number of clicks to complete a mobile task

That “three-click rule” you keep hearing about is mostly a UX myth. Back in 2003, Joshua Porter ran the numbers and found that satisfaction doesn’t actually fall off after the third click, as long as each step gives the user clear feedback. WCAG doesn’t set a hard limit either. In practice, people estimate the total interaction as clicks ≈ screens × 1.5 when a flow is well put together.

Put Steve Krug’s Don’t Make Me Think together with Fitts’s Law (T = a + b · log2(D/W + 1)) and Hick’s Law (T = b · log2(n + 1)) and they point the same way: bigger, fewer targets and shorter menus cut down the time it takes to finish. When you’re designing for cognitive disabilities, the Nielsen Norman Group suggests breadcrumb navigation, a search box that’s always there, and keyboard shortcuts.

Applications

Think checkout flows, onboarding wizards, government service forms, or really any mobile journey where the deeper you go, the more people drop off. To get real numbers, lean on funnel analytics, session replays (Hotjar, FullStory), and a few moderated usability tests.

FAQ

Is the 3-click rule still valid? Not really, it’s been debunked. What each step makes the user feel, how clear and confident it is, matters a lot more than counting clicks.

What is a healthy target tap area? Apple HIG puts it at 44×44pt and Material Design at 48×48dp, while WCAG 2.5.5 AAA asks for 44×44 CSS pixels.

Do back-button taps count? They do. Anything the user has to do adds a bit of cognitive load, so keep those taps down with breadcrumbs and context that stays put.