Really ?

Really Microsoft… Really… (HTC HD7 Bugbears)

Really ?
Really ?

I don’t really consider myself a fan-boy for any single platform, OS or Manufacturer. I have an IPhone which I think is a great day-to-day tool and I have been toying with the idea of an IPad for a while now. On the other hand I’ve been a Microsoft .NET Developer for >8 years now, (saying that made me feel just a bit old…), I use a PC, know v. little about Mac’s and like most things MS. (.NET Dev, Xbox, Win7, etc…).

</Impartial-Fence-Sitting-Disclaimer>

However I was just a bit excited, as I assume most .Net developers & MS Fan-boys were, when they announced the Windows Phone 7, thinking “This is gonna be great”. Alas we got our hands on a HTC HD7 today in the office and my first impressions were a resounding… “Really Meh!”. I’m actually genuinely disappointed with it. It’s not that either the device or the operating system is bad, it’s just not right. It’s like they just forgot to let an actual person use it, and tell them where to apply some polish. Don’t get me wrong, I understand it’s a “Version 1” for the OS, but still, there are a bunch of usability issues (both hardware & software) that within minutes, were pissing me off beyond belief. For me, they were deal breakers.

Before I start ranting, I’d love if people could jump in and tell me I’m wrong. I tend not to be a good “typical end-user”, being a techie and I’m probably quite biased owning an IPhone 4 so maybe I’m off base here.

The Touch Interface.

Person "holding" phone
Person "holding" phone

Hand-model "holding" phone
Hand-model "holding" phone

The HD7 is sporting a lovely big touch interface. The screen takes up the large majority of the front facing panel and the remainder is taken up with 3 Capacitive touch buttons for “Back”, “Home” & “Search”

However since the majority of the surface is touchable with very little dead-zone around the edge, I found myself constantly touching it by accident. Using the device in one-hand, the fore/middle/ring fingers would often make contact with the far side of the screen while holding it steady, causing the UI to be unresponsive to my thumb. And as for the “buttons”, I don’t know why they didn’t go for some actual tactile, clicky buttons here (the least they could have done was dial down the sensitivity a bit). The centre “Home” button is fine but the Search & Back buttons were driving me nuts after only a few minutes use.

The Search Button.

Thumb Triggering Search
Thumb Triggering Search

Pinky Triggering Search
Pinky Triggering Search

By far the most annoying feature of the hardware is the overly sensitive search button. I have no problem with the concept of a context sensitive Search. But the button causes it to constantly pop open, unintentionally during normal use. In my left hand, my pinky finger was constantly triggering it as it wrapped around the bottom of the device. In my right hand, I’d constantly trigger it as my thumb stretched for the far top corner of the screen. In landscape orientation I kept hitting it because I was naturally holding the phone like an XBox Controller. Same while taking a photo and holding it like a camera. Bing Search. Bing Search. Bing Search.

The Back Button.

On the other hand, the biggest nuissance feature from an OS point of view was the back button and it’s complete lack of uniform behaviour. YMMV on this one, but it made me go WTF. This is probably best described with an example. Here’s what happens during browser use over multiple browsing sessions in using both an IPhone & Windows Phone

IPhone & Safari Windows Phone & IE
1. Open Safari and go to www.bing.com
2. Search for “Fish”
3. View the results page
3. Click the link to the wikipedia article on fish
4. Read It & Close the browser
… some time later …
5. Open the browser again, as expected the tab is still there on the Wikipedia Article
6. Press Back
7. As expected you return to the Bing results page
1. Open Internet Explorer and go to www.bing.com
2. Search for “Fish”
3. View the results page
3. Click the link to the wikipedia article on fish
4. Read It & Close the browser
… some time later …
5. Open the browser again, as expected the tab is still there on the Wikipedia Article
6. Press Back
7. As expected… wait what the hell…

Instead I’m brought “BACK” to the home screen. But I wanted to go “BACK” to the previous page in the browser. Oh I can’t do that. Really… Well how to do I go “BACK” in a browser context… I have to press the little star icon? but that means favourites? no? It also means history is hidden in there? Really… Really…

Misc. Annoyances.

There were other things as well that were grinding my gears. Like not being able to find the equals button on the keyboard because you first need hit the “&123” key to get into NUM mode, and then hit the –> Arrow key to have it slide in a new symbol set. And then the equals key appears in the ‘v’ key position of a qwerty keyboard as opposed to where equals would normally appear.

  • Or like how I couldn’t use the market place until we put a sim into the “sim-free” phone despite having already setup the phone with a valid Windows Live Account.
  • Or like how it’s only been in the office for ~6 hours and the front facing speaker traps are already starting to get pretty manky with dust.
  • Or like how it just feels like the build quality isn’t up to par with the kick stand wobbling about and the plastic back cover feeling flimsy.
  • Or like how the camera seems a little bit slow off the mark to auto focus sometimes in what seems like an extremely simple scene as regards light metering & object of interest.
  • Or like how the “People” hub won’t allow me to have two mobile numbers for one contact, nor will it allow me to create custom fields like “Work Desk”, “Work Skypeout” etc…
  • Or like how there seems to be a complete lack of uniformity in the Spelling Case used around the OS. e.g. On the settings page we have:
    SETTINGS, system, ringtones & sounds, theme, flight mode, Wifi, Bluetooth

Really? Either decide on all lower case, ALL UPPER CASE or All First Letter Capitalisation. This sort of mixed case nonsense was just the straw that broke the camels back. Each issue in isolation was a pin prick of annoyance but in a such a short space of time, they all came together in a crescendo, making me want to toss the phone out the window.

At the end of the day, I’ll develop for the platform no doubt, but sorry Microsoft, I shall not be trading in my IPhone for you  just yet… REALLY

Eoin Campbell

2 comments on “Really Microsoft… Really… (HTC HD7 Bugbears)

  1. Stephen Lacy

    Have a windows phone… which I’ve been using for a few days now…

    Having owned an iphone I haven’t been blown away

    I know you spent a great deal of time wording how you are impartial, but you manage to completely ignore and positive aspects of the phone…

    Perhaps in your effort not to be a microsoft fanboi you’ve fallen off the other side of the horse?

    I have found most of the things you mentioned, and they annoyed me too.

    However I’ve found similar issues with the iPhone.. and I got used to them.

    I wouldn’t advise anyone to switch unless they are content with far far less applications.

    For me it was all about being able to write silverlight applications for my phone 🙂

  2. Eoin

    you haven’t been blown away by the IPhone or the Windows Phone ?

    I think you’re missing the point of my post though. I’ll openly put my hand up to being an MS Fanboy. And I think having a phone I can develop on is cool.

    But first and foremost it needs to be a phone-for-phone stuff. MS didn’t build this for the nerd demographic like you & I who will buy one regardless because they want to develop silverlight apps on it.

    And as a consumer phone, my humble opinion is while it’s a good first step, it’s lacking enough on the UX side not to make a good enough dent. 6 or 8 people (devs, QA’s & biz) who’ve played with it here in the office seem to agree.

    Bottom line is, my IPhone is more useful to me as a day to day tool, so the WP7 gets relegated to the drawer for dev-use only.

Leave a Reply

Your email address will not be published. Required fields are marked *