I find this to be much easier and faster than using the Info window or the delightful "Click to select. Wait a moment and then click again to toggle editing, but don't click too soon or else it'll be a double-click and you'll start to play the item."

If you're a Windows user I assume you press F2 to rename an item, but I've never used iTunes on Windows.

I don't think I'd ever say that about an iPad – even if the reading experience was superior – because an iPad will always be a computer first; everything else is secondary. The Kindle was designed to replace books, not let you read books, watch movies, listen to music, browse the web and play games.

If you're building a single-purpose device there shouldn't be any compromises with the design, and the overall experience while using it for its sole task should always be more enjoyable than with a multipurpose competitor.

I don't want my Kindle to do more, I just want it to be better at what it already does.

- Security is using HTTPS to encrypt traffic between my browser and the web server.

- Security would be to have the page automatically time out and redirect to a page without any of my personal information.

- Making me re-enter something I just typed because I forgot to fill out a form field is not added security, it's just inconvenient and annoying.

The same is true for sites that believe using fields with TYPE="PASSWORD" to mask the text somehow increases security. I have no empirical evidence, but I'm sure those forms are re-submitted significantly more than non-obscured counterparts. At the very least it makes users want to bite your face.

Android users complain that they can't install the newest OS on their device, that Exchange sync doesn't work, that third-party applications crash, that Android Market is horrible, that core applications crash, that settings are obtuse and scattered, that it's awkward to use and uncomfortable to hold, and even though the browser uses WebKit, it sucks.

Two generations of phones later, and all of the current iPhones are capable of running the latest OS from Apple. Third-party apps exist, and for the most part don't crash. Except for hardware differences (GPS, speakerphone, camera), most applications run on any of the 6 iPhone and iPod Touch devices. Even the screen doesn't get greasy any more, and Apple introduced the word "oleophobic" into the vernacular. The major failure is still AT&T, who apparently uses frame-relay and microwave links for their backhaul.

Meanwhile the problem with Android devices lies much deeper. SDKs aren't released until weeks out after an OS release, resulting in masses of applications that aren't compatible with the new OS release (and with the newest device, as long as Google continues their new device, new OS trend). The Android Market is a mess – applications are being published that steal personal information, easily half of the apps are filled with comments to the tune of "doesn't work on device XXXX" or "crashes immediately!" because of the massive API changes occurring between OS releases and developers that lose interest after a single application.

Notification controls are non-existent – I have yet to find a way to shut my Droid up. Even if I go into every application and turn off all the sounds (and boy is that fun) and shut the phone off, for some reason the Motorola demon spawn will power itself back on and chirp at me.

And the browser. Oh the browser. Sure, it renders pages fine, but it's slow, and doesn't support multi-touch. The screen itself is capable of supporting multi-touch, just not the browser. The free Dolphin Browser has tabs and multi-touch gestures, but shares another flaw with the bundled browser – animation speed. Animations take much too long. Aim for about 200ms from start to finish. Any more than that and users will become impatient. And after waiting 600ms for a pinch-to-zoom, impatient is accurate.

Apple has demonstrated that they listen to user complaints, or at least that they plan ahead well. Most of the iPhone complaints were addressable with newer hardware, but the problem with Android is that Google seemed to want to take the exact opposite tact of Apple, and go for complete openness. That's great, but it looks like they started by attacking standard UI controls and behavior. Maybe they consider it a feature? ANDROID – where every app is so different it's like having 15 phones in one!

Google needs to tighten up the operating system and address the sprawl of OS releases and devices quickly before they fall into the same trap that RIM is in – a nasty pit one where a developer has to build multiple versions of a single application to overcome massive feature disparity between OS releases¹.

1. Although in RIM's defense they're addressing this with OS 5.0 which has a unified codebase. If only the carriers would get off their asses and approve the 5.0 updates.

Someone hooked me up with a new pre-release BlackBerry 9700 last week (just in time for the BlackBerry Developer Conference), and unfortunately it still doesn't allow you to charge the phone while it's holstered.  When it comes to usability this is pretty basic shit; instead users are presented with a few millimeters of stupidity.  At least the USB port is at the top of the device, so you can set the phone vertically into a car cup holder with a charger connected, one more place the design of the Storm 1, Tour and 8900 fails.

My high-school French teacher¹ used to refer to screw-ups like this as "mansy-pansy junk" (or something along those lines), and I suspect he'd be just as disappointed with this as he was with what he referred to as my "Franglais".

1. Hat tip to Mr. Bergeron