I am more bothered by the chaos on the SD card, and the apparently complete lack of guidance from Google on standard locations. It's just a mess of root directory folders of arbitrary names. You hope that your selected media directory names won't conflict with something that an app may choose in the future. (I personally use _music, _video etc. both to avoid conflict and to come up top in most alphabetical listings.)
For starters, that it's necessary at all! The first devices all had only 256mb of flash, but then the OS got bigger than that (can't upgrade older devices cleanly!), so they just doubled that to 512mb instead of doing anything sensible. Is there a single "Google Experience" Android device with more built-in Flash than that?
What's worse is that they use it sparingly themselves but essentially force everyone else to -- Apps don't fit in the onboard flash, you can't even run Apps from the SD card, so everyone has to hack together their own asset system. Now the SD card isn't removable without breaking your running apps!
It's a heap of ill-considered shit. Nobody would even propose these idiocies at Apple, much less get them past their manager. Even Windows Mobile wasn't this bad, but mostly just because they didn't try to do very much. The Android team thinks they're clever -- but when the WM diaspora (http://www.xda-developers.com/) are the community that fixes up your shit, you're clearly not.
They really shouldn't be exposing a shared RW traditional filesystem to apps at all, no matter where it's located. Unfortunately that's the only API they exposed!
They really should be forcing manufacturers to ship with at least 8gb of flash to get the "Google Experience", but instead even their Nexus One ships with as little storage as possible to save a couple dollars!
My whole point is that the SD card SHOULD NOT be used as a permanent component in the OS base system at all. It should be removable storage, but the way apps are forced to use it makes it anything but!
The whole thing is completely incompetent. It would have been hard/impossible for them to implement removable storage to Apple's standards of usability, but they could have at least done better than WinMo! Really they should have just shipped the original devices with a healthy amount of flash and no SD card slot at all, and added removable storage support in a later iteration (which is exactly what Apple did).
In the Pandora system, we have PND files, which solve this problem pretty well. Perhaps Google can consider something similar:
http://developer.android.com/guide/practices/ui_guidelines/i...
... but it is certainly true that there is no review or enforcement mechanism in place to help developers conform to these guidelines.
Having a standardized Back button allows me to reflexively hit a button with the expectation of returning to the previous screen without needing to pay attention to what application I'm using or where the UI designer decided to place the button onscreen.
Having a standardized Menu button allows developers to place options or advanced workflow mechanics in an easily-discoverable location without needing to dedicate screen space to more buttons. This means more of the gorgeous touchscreen can be devoted to content I care about, and not the buttons that every application should have in the first place.
The iPhone's approach of putting these buttons on the screen has the major advantage that they are only visible when they actually have a purpose. Usually, the buttons are also labelled more specifically than simply "back" or "menu." For example, if you're looking at your folders in the Mail app, the back-equivalent button is labeled with "Accounts," indicating that hitting it will take you back to the accounts list. Also, the lack of a "menu" button discourages developers from just shoving everything into a menu. The result is that more common operations end up directly accessible (and immediately visible), while less common operations (if any) are usually tucked under a menu-equivalent "more" button.
The potential inconsistency in semantically-similar button placement between applications is mitigated through HIG enforcement. In practice, it's not an issue.
tl;dr: putting buttons on the screen instead of using physical buttons increases predictability.
* That said, I've gotten pretty good at predicting what back will do after several weeks of using my device (with the notable exception of GMail, which breaks back button behavior spectacularly). This was a huge pain point when I first got my device, though.