Positioning of buttons on iOS is a big problem.<p>For instance, when on a phone call and you show the numeric keypad, there is <i>no</i> sane reason to make the &quot;Hide&quot; function a microscopic text label that is a finger-width away from the <i>HANG-UP</i> action.  Functionally, these actions should be on opposite sides of the display from each other.  I don&#x27;t even think they placed it there for aesthetic reasons, since the Hide &quot;button&quot; just looks like an ugly hack.<p>Then there&#x27;s positioning of keyboard keys.  If I had a nickel for every time I deleted a character while trying to finish a word with &quot;m&quot;, or every time I accidentally <i>committed</i> an action with incomplete text because of that stupid blue key!  Instead of moving dangerous actions to the <i>opposite end of the screen</i> where they belong, too much effort was spent trying to emulate the precise layout of a real keyboard.  I don&#x27;t think users would complain at all if the &quot;action&quot; key was instead in the top-right corner, and if &quot;backspace&quot; was in the top-left corner.<p>The scrolling calendar widget is also a nasty example of poor positioning.  Long after it was &quot;improved&quot; in iOS 7, I <i>still</i> can&#x27;t create a single calendar event without doing the accidental-screw-up-date-instead-of-scroll action, usually with &quot;helpful&quot; automatic &quot;corrections&quot; for my change such as synchronizing the From and To times to both reflect my accidental date-change.  Or if I&#x27;m really lucky, I don&#x27;t even notice that I changed the time.<p>They need to step back and realize that design is how it <i>works</i>.  Their interfaces are incredibly error-prone right now.