Seven days with the Samsung Omnia 7 Windows Phone 7

One of the perks of working in software is occasional access to sweet, new hardware.  I’ve befriended the super-busy Mobile team at the office, and asked to borrow one of their spare Windows Phone devices.  Craig handed me a Samsung Omnia 7 and asked me not to destroy it.  I had been wary of the Windows mobile experience having used Windows-based Palm devices (not great compared to their PalmOS counterparts), but had been prepped by blog posts that this Windows Phone 7 experience would be totally different.

Short story: the hype stands up – the user experience of this phone is excellent.  There are small issues that I’ll go into in detail including frustrations with the hardware design, but ultimately the overall package is slick, functional, and at times even beautiful.

The Hardware

The physical hardware of the phone is a generally great.  The phone has a large, bright, and easy to read screen, a single recessed button, very few creases and edges that collect dirt or grime.  No MicroSD card slot, but lots of RAM.  Normal (3.5mm) headphone jack that took my iPhone mic’ed headphones just fine.  The light vibration you get when you touch the dedicated “back” and “search” areas reminds you that this device is very touch sensitive.  VERY touch sensitive.  In my first day or two of usage I pocket-dialed, Facebook’ed, mapped about half of my contact list – until I learned to lock the device every time I wasn’t explicitly performing an action (with the dedicated “lock” button).

The lack of physical keyboard made my transition from a Blackberry Bold difficult for typing-heavy tasks like email, though the live spelling correction works great.  The orientation sensing works well (smooth and predictable), so I learned to type my emails with the phone laying horizontally, with just a few lines of my reply visible outside the on-screen keyboard.

Compared to my Bold, the reception was weak.  I dropped out of 3G far more often than I’m used to.  The point here is that Blackberry devices have great reception, more so than the Samsung having poor reception.   Same goes with the battery life.  On a full-night charge I got 8-10 hours of normal usage including WiFi internet and calling at a business-user level.  Apparently that’s endemic for these large touchscreen devices.  Definitely not a showstopper, but news to me.

Search Button :(

Lastly, the dedicated search button got in the way far more often than I found it useful. For example when I was holding the phone with two hands when taking pictures with the Samsung’s excellent camera, I would accidentally press the search button and jump out of the Camera app into Bing Search.  Oh man, that happened about four times before I started digging through Settings to try to re-map (or at least disable) the search button.  No luck.  This is my least favourite feature of this phone, and I would gladly do away with it (or at least have it recessed so the click has to be more deliberate).

The Software

This is my first look at the Windows Phone operating system, and a it’s stunning piece of software.  The lack of fake 3D buttons was jolting and refreshing.  The home-screen Tile view is far more useful, customizable, and interactive than any other phone home-screen I’ve used.  Little features about the tiles were really nice: when you drag the screen the drag arrow gracefully rotates, the numbers for email counts flip rather than just changing, the text messaging tile gives me a wink ;-) with one message, and an Oh No! face :-O when I have four unread text messages. All of it seems refined, friendly, and inviting.

The Little Things :)

I started customizing my home-screen immediately – added all of my frequently-called friends to the home page, local weather, Twitter, Facebook, work Outlook (seamless), personal email (less than seamless).  After the second day, I rarely ventured past my home screen other than to browse Facebook and play with phone settings.

The ability to bundle contacts from your phone with ones from Outlook, together with their Facebook profiles was amazing.  My friend Mike has three different identities on my Blackberry (unless I go through contact-synch hell to combine them), while he has only one on my Windows Phone, which is hugely convenient.

One thing that is often not well executed on phones is a good range of alerts, alarms, and audio stuff.  It’s obvious that great care went into the audio landscape of the phone. The clicks, pings, boops sound downright beautiful.  The alarms are gentle but effective, rather than being grating and amateurish like some Linux sounds (*cough*).  The external speaker could be louder in phone-call-at-the-train-station situations.

Considering this phone and platform is new to the market, I was impressed by the availability of applications (as I read that is one of the fatal flaws of this platform).  I know that Microsoft has been shitting bricks about the app experience as it compares to the Apple App Store, but Facebook, Twitter, Score Mobile, Yelp, and many of my favourite heavyweights were there, and were executed pretty well.  There is no Google Maps application available, and the Marketplace in general has some obvious holes – Foursquare, for example, but apparently that’s coming soon and it’s hawt as hell. Bing Maps isn’t as good as Google Maps, as the location based searching for stuff sucks in Canada and elsewhere outside of the US.

The Facebook app doesn’t react as well as it does on the iPhone, as everything is clickable … while nothing is a button. There’s a theme of explicit “this will do this” actions being ambiguous in these apps, so I ended up changing screens and navigating away by accident – a side product of the really fluid and draggable design of the operating system.

While this may not be a highlight for a lot of people, the integration of Office viewers for Powerpoint, Word documents, and other documents was welcome.  The experience with attachments from within the email client was the best I’ve ever dealt with, and made both the Blackberry and Apple offerings seem Web 1.5.  This isn’t game-changing behaviour, but certainly helped me get over previously discouraging experiences with document-handling on my phone.

Overall Thoughts

The combination of the hardware and new Windows Phone 7 software is immediately slick and usable. Little touches such as the smooth transitions, crisp fonting, and contact linking are a pleasure.  The hardware such as the case and camera are first rate. The touch sensitivity of the device has forced me to pick up habits that I don’t love (locking the device constantly, being careful about interactions in Facebook, etc.) and the “search” touch button is infuriating when I’m in a hurry trying to take a photo. This being my first introduction to Windows Phone / Mobile 7, I am excited about its future.  If anyone is listening, bring on Google Maps and Skype, please :-)

Little Bugs

This is a list of bugs I came across that didn’t warrant being in the main review, but hopefully will get addressed as the platform matures:

  • Something is off about the audio system.  Occasional jitters, noticeable when you’re playing games or are doing web browsing that involves sound, were a nuisance.
  • You have to click “all” photos before being able to see the ones you took with your camera (“Camera Roll”), rather than having them show up on the front page of the Photos app.
  • After the phone is unplugged from its charger, the little charge indicator stays on, sometimes until the phone is turned off.
  • Making corrections to settings when setting up an email account requires you to retype everything on every retry.  Super annoying when you’re trying to debug your email connection.
  • Can’t change which Windows Live account is associated with your phone unless you do a software reset?! A bit ridiculous.

Presentation on Accessibility and Design on Jan 20, come!

For those of you in Kitchener-Waterloo who are into web accessibility and product design, myself and Ali Ghassemi are doing an hour-long talk at the next uxWaterloo event on January 20, 2011 at 5:30pm.  We’re super excited!

The focus will be practical advice for designers and developers about building accessible web applications. Ali and I will have lots of examples of specific things that need to be considered in the design, development, and testing stages, as well as make a case for building with open standards. In general, the hope will be to provide attendees with a rich overview of the challenges, make A11Y less scary by sharing specific anecdotes.  It’ll be a design oriented presentation, but both Ali and I are versed pretty well in the technology if you care to Q&A!

We won’t be focusing a lot on the legal responsibilities surrounding accessibility. I find too many introductory discussions focus on the legal issues first, thereby mentally cheapening the problem to one of WCAG compliance. Accessibility is one of the most interesting user experience problems the web has to offer, so I feel it deserves a more nuanced design discussion.

So yeah, please register on the uxWaterloo site if you’re interested.

There’s also a Facebook event, if you want to share the news.  My lovely employer Desire2Learn will be hosting the event (it won’t be at the Accelerator Centre).  Looking forward to seeing you there!

Explain your job to someone in 1950

Sometimes my mind is blown about what I actually do for a living, just based on the fact that I have a really hard time explaining it to people. Despite being in a world where cell phones, the internet, and Microsoft Office are part of the daily fabric of life, how many of us are aware of the finer points of creating this software?

So as a fun little exercise, a colleague of mine at work (Michael Swart) was wondering how one would explain their job to someone in 1950 – a time before computers.  His explanation inspired this post.

Explaining it in 1950

Grandma and Grandpa Suski in 1953

Grandma and Grandpa Suski in 1953

All of us use some sort of tool to help us with our jobs -  a sewing machine, a reciprocating saw, or a typewriter. When you use that thing, you can tell if it has been well designed. Does it do what it’s supposed to do, and does it in such a way that makes that task easier? Does the spindle move without jerking, does it stop on a dime, do the keys mash or click gracefully?

It’s a little more abstract, but think about reading a book. The form of the book itself makes a big difference in how you you read – are the pages a pleasure to flip, is the print too small to read on the trolley, does it stay open or force itself closed, does it look rich, cheap, well worn, or brand new?  All of those things are part of the design of that book, and that’s what I do – but not for books.

In the future, reading and writing will not be done with printed books and pens, but with a device called a computer. Computers will have  television screens that can show words and pictures (rather than printed paper), and be hooked up to typewriters. This is how schoolchildren will read and write, teachers teach, and most of us send letters and notes to one another.

Computers can do many, many different types of things – each one of these things is called a program. I work for a company that makes computer programs for Universities. My boss tells me “improve this program where people write mathematics equations”, or “make sure that Chinese people can use this as well.”  I work on a design for a program, that runs on a computer.

I work with a small team of people: I figure out how a program is supposed to look and behave. Others work on the nuts, bolts, logic, and engineering. Others make sure it works how it’s supposed to (quality inspectors), others write the manual, and others still deliver it to the client, and help them use it. It takes months, sometimes years, for a program to be “done.”

Believe it or not, someone pays me good money to do this. :-)

Aiming for Accessibility Conference

Desire2Learn sent me to the Aiming for Accessibility Conference at the University of Guelph for one of the two days, and it was a really solid.  There’s quite a bit of expertise around accessible web technology here at the office, so it’s nice to see the cause celebrated and discussed.  The conference wasn’t huge: intimate and loaded with experts in the field, so the learning opportunity has been sweet.

Presentation

I put together a quick presentation [PDF] of the stuff that stood out for me, and presented it at a “lunch and learn.”

My co-presenters and I expected 5 or 6 people … instead we got a full room of about 20.  Super happy! It was good practice for a talk I’ll be doing at Fusion 2010 about accessibility and internationalization (3:45pm on the Tuesday).  Doubt I’ll be able to share any information from that one, but just wanted to advertise :-)

Highlights

All content in there copyright of the respective presenters.  Highlights include:

  • Adaptech’s study of social media usage amongst disabled students in Ontario produced a great list of which social media services are and are not accessible. Facebook good, Digg bad, surprisingly.
  • It’s important to understand that students with disabilities generally don’t want to identify as “disabled” online.  Often clicking on “Accessible Version of this!” leads to  a simplified, crippled (forgive the allusion) web experience, rather than the rich experience they would expect from a website (and other students get).
  • Content creation is further behind the times in terms of accessibility than the web frameworks / CMS’s are.  Partly this is because content creators come from a visual design background, and may not appreciate the content over the presentation. The key here is bridging the content to data gap using XML, and tools that support it such as Adobe InDesign.

Chrisitian Rohrer’s Greatest Hits

Whenever I try to frame a usability problem we have with some sort of solution, I usually get overwhelmed.  Usability research is difficult to execute well even if you know what you’re doing .. but UX is a field with an over-abundance of methods and strategies.  All of these strategies have pros, cons, proponents, and detractors, academic and otherwise.   Luckily every once in a while I run across a paper that attempts to frame all of these methods in some sort of matrix that I can make a business decision on. I can have a hunch, go to my manager, point at graph, say “we should do 2 of these.”   Christian Rohrer‘s presentation to BayCHI is one of those useful papers.

desirability matrix

Slide about quantifying desirability - Like whoa ...

His original presentation and blog article have links to the PDF, as well as a link to buying the presentation for $70 or so.  We watched the presentation at work and it’s … not great for a group audience. The slides read better than they are presented, but I can’t fault Christian for this .. just the sheer amount of good content is overwhelming.

User Experience Leader Christian Rohrer provides a framework for understanding and explaining different user research methods, delves into details on a few of the lesser-known methods, such as desirability and true intent studies, and discusses key insights to succeed in modern-day corporate environments.

PDF download

Sorting Country Names in their Native Language

I used to think that sorting things was easy. Collation is a really difficult problem, especially once you start considering different script (Latin, Chinese, German, etc.) and numeral systems (Western Arabic, Hindi, Japanese, etc.) in the same list, not to mention locale-specific sorting irregularities like German Phonebook sorts.

The problem of sorting country names is particularly sensitive.  When you want to display China as 中国 to Chinese speakers, where should it be sorted compared to Canada or Kâmpŭchea (Cambodia)?

Here we have an example list of countries, in the order I looked them up online, heh.  For the sake of not messing with my blog, I avoided Right-to-Left country names for Egypt, Iran, or Israel.

  • United States
  • España
  • 中国
  • Deutschland
  • Polska
  • Россия
  • भारत

If you had a “sort” feature in whatever software you’re using, hopefully it’s using the Unicode collation order to sort the names. You typically would get something like this as a result:

  1. Deutschland
  2. España
  3. Polska
  4. United States
  5. Россия
  6. भारत
  7. 中国

Business Case Sort

Alpha sorting, Unicode or otherwise, may seem pretty arbitrary especially if 95% of your customers come from three or four countries.  One can always make the case for sorting country lists with the most popular countries dominating the “top 5″ or so of the list *. For many businesses this may mean a sort order of:

  1. United States
  2. 中国
  3. Россия
  4. Deutschland
  5. España
  6. Polska
  7. भारत

That’s all good … if you want to confuse Indian and Polish visitors, don’t care about keyboard users, and want to take a big hit on your Russian branding.
* Instead of mucking with collation, a usable solution is to autodetect what country people are from and pre-selecting things in dropdown lists, or highlighting it as a choice outside of the sorted list.

ISO to the Rescue

In my research, I’ve found a pretty good general solution, irrespective of the business case, is to sort things according to the ISO 3166-1-2 code. I know, I know, it’s lame and old and under fire constantly .. but it’s a fairly standard coding that technical people understand, native speakers understand, keyboard access is alright, and it’s considered safe on the culture-war front (other than being based on the Latin alphabet).

Our example above would be:

  1. 中国 (cn)
  2. Deutschland (de)
  3. España (es)
  4. भारत (in)
  5. Polska (pl)
  6. Россия (ru)
  7. United States (us)

Anywho, that’s just my suggestion for a starting point. Your business case may indeed support other sort orders for countries.  But this one is reproducible and defensible, so that makes it good for programmers and business analysts alike.

Blue Beanie Day 2009 @ Desire2Learn

blue beanie day

blue beanie day. Originally uploaded by jclhicks.

So some of the design and standards people at work wore blue toques today in celebration/encouragement of designing with web standards:

Doug Vos’ Writeup on Blue Beanie Day 2009

If you’re interested in showing some web-standards solidarity, take a look at the Facebook group.  We’ve been really struggling at the bleeding edge of ARIA and other web-application accessibility stuff lately, so some encouragement (especially from the browser and assistive technology vendors) would be appreciated!

The birth of the Microsoft Office “Ribbon”

New ideas for user interface components don’t come by very often.  For example, the pointer, icons, and toolbars have been around since the late 1970′s courtesy of the work done at Xerox PARC.  It’s safe to say that the computing environment in the late 70′s was quite a bit different than it is today, so it’s only logical that some of the paradigms developed then need a modern refresher.

There have been high profile attempts at designing new, complete, usable components to solve specific problems such as interactive assistants and horribly bloated CD lists.  But in recent memory, all pale in comparison to the Ribbon that Microsoft introduced in Office 2007.  The Ribbon is what replaced the toolbar system used in previous versions of Microsoft Office.

office ribbon

The ribbon effectively solves the problem of displaying the functionality of a very complex and feature-rich piece of software like Word or PowerPoint much more effectively than toolbars, tabs, and other competing concepts.   In combination with gallery views of icons, and organising things in use-driven groups, the solution is elegant and ages well.  It’s unfortunate (read: fucking brutal) that Microsoft is patenting this idea in the current climate of software openness and growth, but I digress.

Jensen Harris did a presentation at MIX ’08 about the history of Office and how the ribbon was developed.  A must watch for any employed interface designer:  the ideas about religious tenets, building lots of high-fidelity prototypes,  evaluation over a number of months, and constraining ideas to make reasonable decisions are worth discussing.

YouTube video below, but the complete presentation is available from Microsoft.

Internet Literacy in Education

Wanted to share a pretty great video about internet media literacy, and higher education. For someone finishing up a Masters, some of the points he makes ring very loudly. From the YouTube video:

Recently Dr. Wesch spoke at the University of Manitoba where he explained the the basis of this video in a talk entitled, “Michael Wesch and the Future of Education.” I found it fascinating! He describes how he so naturally incorporates emerging technologies into his courses from the smallest seminar type class to the largest lecture theatre filled class.

More importantly he not only talks about the technologies but how he encourages extraordinary participation and collaboration from his students by engaging them in meaningful learning activities.

[...]

During his presentation, the Kansas State University professor breaks down his attempts to integrate Facebook, Netvibes, Diigo, Google Apps, Jott, Twitter, and other emerging technologies to create an education portal of the future.

An actually useful poster from the UPA

This has to be one of the most functional and relevant posters I’ve ever put up on a wall.  It’s from the UPA (Usability Professionals Association) and it briefly goes over and organises the process of designing software for the user. I got one mailed to me when I joined the UPA as a free gift.

The poster is incredibly rich with information.  It goes through analysis, field studies, creating user profiles, documenting requirements, designing, verifying with users, prototyping, implementation, heuristics, usability testing, and the rest of the steps.

The 11×17″ poster [PDF] is just as detailed as the full-sized one.

As found on mprove.de.

Proudly powered by WordPress
Theme: Esquire by Matthew Buchanan.

Switch to our mobile site