Unless we're speaking very narrowly in terms of hardware, I disagree. I've never used Android on the tablet, but I've owned Android phones for years. I own an i

Unless we're speaking very narrowly in terms of hardware, I disagree. I've never used Android on the tablet, but I've owned Android phones for years. I own an iPod Touch and an iPad. The device's interface and the way it influences apps & app developers makes a huge difference. On Android, menu is functionally equivalent to right-click, which means it either hides complexity or it's a dumping ground, depending on your perspective. I don't care for it. The lack of a OS-level back button on iOS means most apps put a back button somewhere on screen, or there's page-swiping. Generally you know where pressing that button will take you. The vast majority of the time it will never take you out of your current application. That is not the case on Android; you can dump yourself back to the home screen from a web browser if you hit Back one too many times. And then there's the "activity stack," an OS-level concept that interacts with the Home and Back buttons. Maybe the buttons themselves are not differentiators, but they imply or enforce different assumptions which in turn inform the way people use and develop for the device.