'Why did Apple not include radio buttons in Interface Builder?

I realized that people have been implementing their own UIButton derivates to create radio buttons on iPhone, as this blog post shows.

This question's accepted answer states you can use Picker Views or Grouped Table views with a check mark, but it seems like a poor man's solution to me. Hence, my question: what is Apple's likely reasoning?

  • Are radio buttons a bad UI solution for touch interfaces?
  • Is it so rarely used that it's not worth cluttering IB with?

Another reason I don't quite see, maybe? I believe it's important to find this out, because if Apple thinks radio buttons suck, I'd rather not use them, and rethink my interface whenever I "believe" I should use one...

iphone


Solution 1:[1]

Radio buttons are a bad UI solution if they are poorly implemented. i.e. too small to reliably work with touches - which is why it's usually better to either use a toolbar or segmented control of options or a tableview of options.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1 ader

Related Questions