Skip to main content

Minimum sensible button size on iPhone



I'm designing an iPhone app that features a rather large set of onscreen rounded rect buttons. Given finger-based touchscreen UI, what do you think would be the smallest sensible button size? I need to fit as many of them as I can in the viewport without compromising the usability too much. Maybe there's an Apple-recommended minimum size? Right now it's 33x33, and it looked OK on a simulator, but I was playing with the app on a real phone last night, and it was awkward - the buttons felt too small.




Comments

  1. Apple says that the avg finger tap is 44x44 (from WWDC). All table rows are recommended to be at least that height. It is common for icons to appear 32x32, but have padding to make the touchable area 44x44. Of course, people can tap a 1x1 if they are very careful, but why make people try harder than they need to in order to use your app?

    ReplyDelete
  2. Recent scientific research has found that:


    [A] target size of 9.2 mm for discrete
    tasks [i.e., single-target pointing tasks] and targets of 9.6 mm for serial
    tasks should be sufficiently large for
    one-handed thumb use on
    touchscreen-based handhelds without
    degrading performance and preference.


    Cited from Target Size Study for One-Handed Thumb Use on Small Touchscreen Devices (Parhi, Karlson, & Bederson 2006). Other sources agree on this "close-to-0.4-inch-rule" (e.g. Designing Gestural Interfaces (Saffer 2008, p. 42)).

    Given the iPhone's pixel density of 163 PPI (6.417px/mm), you should preferably aim no lower than 59px diagonal for any target.

    (Please note that this is verified for one-handed thumb use only.)

    ReplyDelete
  3. Apple is not consistent in this, and there are no hard rules.

    They recommend you provide Fingertip-Size Targets in the UI Guidelines, and then go on to say that the calculator buttons are 44x44.

    Also in that document they say that images for toolbar and navigation icons should be 20x20, and for tab bar icons should be 30x30.

    I think you have to simply test your application and make sure that it's easy to press the buttons - even when you have fairly large hands...

    -t

    ReplyDelete
  4. I could have sworn they said the minimum was 37 pixels, but I'm finding 44 today. Either way, 33 seems small.

    (Note that images can be smaller because they're often part of a larger rectangular area.)

    (You might get away with fewer pixels on other devices, if the pixel size is larger.)

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex