Inline Autocompletion

Inline autocompletion is a common part of search bars, but for the longest time, autocompletion was anchored to the beginning of the URL in a web browser address bar. In the middle of last year, Firefox included an "awesome bar" in version 3, which allowed us to type: "lunar" to bring up a past history or bookmark of "http://en.wikipedia.org/wiki/Penumbral_lunar_eclipse", whereas other browsers required typing, "en.wiki..." (not even flexible enough to allow "wikipedia" to yield results). Over a year onward, and this still hasn't spread to other browsers.

Inline autocompletion

Anchored autocompletion

Seeing as most web browsers haven't integrated their search and URL bars entirely as Chrome has, this is one handicap of most browsers that maintain discreet address bars, as they miss out on one of the top usability benefits of unanchored autocompletion - lessening the requirement on the user to remember URLs.

Browser Sniffing on the Mobile Web

Browser sniffing holds a level of stigma in the web development/design world, as we have been spending years and years creating cross-platform, cross-browser sites that use more robust techniques of singling out browsers, rendering engines, or platforms as a last resort through our knowledge of what's supported - CSS conditional comments, JS object detection, and various tricks and (if needed) hacks both client and server side. It has long been our practice to create a solid separation of presentation, content, and functionality in a way that degraded gracefully (or more recently, progressively enhanced).

This has worked well on the desktop platform, from desktop workstations to notebooks to tablets.

The Age of Rich Mobile Computing

So the question becomes, what to do with the mobile platform. For years, there have been very basic mobile-specific pages for basic phones with tiny viewports and browsers that couldn't handle much more beyond HTML, with notable omissions of support in areas like CSS and Javascript.

But ever since the iPhone brought fully-featured mobile browsers to the mainstream, there has been this huge trend of companies creating iPhone-tailored sites designed for the width of their viewports, and guaranteed to work on W3C standards-compliant browsers, including Webkit-based ones like MobileSafari, and soon after the ones on the Android and webOS platforms, which currently also have devices with similar viewports. Consequently, these iPhone-tailored sites generally automatically work well with most modern smartphones with full browsers, effectively creating a second tier of mobile sites for smartphones.

For the iPhone initially, it seemed both sensible and insensible simultaneously that people were creating sites that fixed themselves to a specific viewport width. One of the great abilities of MobileSafari on the iPhone was that zooming on small screens was finally easy with the pinch gestures, so coupled with the full HTML/CSS/JS browser, there would be little reason not to experience the same full website used on the desktop platform. Even considering this, however, people still designed sites that negated the pinch zooming.

Still, with a smartphone version of the site, you would ideally be served the same information you need in a way that didn't require any zooming at all, because the user is still otherwise pinching his way into a zoomed out preview of the page that he can't initially read. But sometimes smartphone sites aren't thought out as well, and information or features end up missing.

In some cases though, desktop versions of sites are so mobile-unfriendly (Facebook desktop site) that we pretty much have to rely on mobile sites or native applications to access them on mobile devices.

But there's a lingering question that we may all face in the coming years - at what point is a device considered a "mobile" device and not a desktop computing device?

Drawing the Line at "Mobile"

In late 2008, I had this discussion in an iPhone development forum where I wanted to know how to allow a user to use a link to exit a mobile page back to the full desktop site, without cookies and without having the desktop site's mobile browser detection causing an infinite cycle between the desktop and mobile sites. In other words, just as many sites were doing, I was automatically directing all appropriate mobile devices to the mobile site, but wanted to offer an option to return and remain at the original version.

We came up with a solution, but not before having a heated discussion over whether browser sniffing on the mobile platform was a forgivable exception. My point was that most phones beyond the iPhone did not possess easy pinch zooming, and magnifying with a trackball one square block at a time was not a pleasant experience. Beyond that, there were functions most mobile devices could not yet handle so smoothly, such as click and drag, and general mobile-specific features like data detection (phone numbers, addresses for maps, etc).

But the best counter argument I heard that makes me reconsider is that the line between desktop and mobile computing is not as clearly defined as we think, especially if you think about the smaller 7" netbooks in the middle of the spectrum with screen resolutions in the 800x480 pixels.

It's possible this gap could shorten and fill over time with in-the-middle devices like these and other devices with smaller resolutions. For comparison, the iPhone family of devices sports a 3.5" 480x320 pixels screen.

It's also possible this gap might remain as sparse as it is today, if we assume that the 7" netbooks are roughly the smallest non-niche form factor the mainstream is willing to bear on a desktop platform with a two-handed QWERTY keyboard, and that today's smartphones with thumb-based QWERTY keyboards (hard and touch-based) are in the upper bound for mobile to remain pocket-friendly.

Ideally, we do want our fluid layout pages to scale down well to the current mobile category of devices, and not to serve and maintain special mobile versions of our sites. As it stands, the gap still holds, and for the sake of the user experience in the present day, this is how many of us will approach it. We'll see where the future takes us from there.

Thoughtful Charts and Real-Time UI Feedback in Google Finance

I'll have to admit that I've never been a frequent user of the advanced options of Yahoo! Finance, so the information that Google Finance provides is just right for finance users like me who just want the fundamentals, and Google Finance has provided excellent usability for that.

One of my favorite features that came out of Google Finance was the extended hours trading on charts of logged in users. Real time quotes in after hours trading was already common in both Yahoo!'s and Google's finance products, but visually displaying the pre-market and after-market movements diagrammatically was important because it displayed the history of the price movement per share of a stock, whereas beforehand, you only had the current trading price during active after-hours, or the last price after that session had ended. It has also been a particularly useful way to guess the trend to be at the opening bell.



A couple days ago, they introduced a tiny detail that I believe users will find helpful - any digits changing in the displayed price will flash green or red momentarily, depending on whether it's an upward or downward change. To put it in perspective, the norm before this was to only color-code the difference in points or percentages, not any part of the price itself. This is a small step, but it reminds me of the days in the late 90's when CNBC turned their navy blue change indicators and values to color-coded green and red values, a novelty that has long since become a standard.



Beyond that, still among my past favorite interface details are - showing news indicators on the charts at the point where news was announced, and transactions tracking to monitor gains and losses. The next step would be to somehow make this site scalable on a mobile viewport, the Flash support on various mobile devices notwithstanding.

Window Maximize and Zoom

The other day, my friend Eugene and I were discussing zooming and maximizing with regards to window management, as he was looking around for workarounds to maximize windows in OS X. The zooming function in OS X, represented by the green orb button, is the counterpart to the maximizing function in Windows, represented by the maximized square. Yet unlike the parallel "close" and "minimize" functions, "zoom" and "maximize" are not equivalents of each other.

The "maximize" button in Windows expands the current window to fill the entire screen.

Whereas the green "zoom" button on the top left corner of every OS X window toggles between two window sizes. One is set by the developer, most commonly fit-to-content (e.g. Apple applications and most programs), but also fit-to-screen (e.g. Firefox). The other is defined by the user, so if you resize the window to 800 pixels wide and 600 pixels tall, that will be the saved setting whenever you toggle back to the user zoom.

Zoom 1: User-Defined Dimensions

Zoom 2: Fit to Content

This was one of my own habit adjustment hurdles when switching from Windows to OS X, and apparently, it was also one of the most common adjustments users migrating from Windows had to make. Coming from years on the Windows platform, we liked to maximize, maximize, maximize, and apparently it was a common complaint of those migrating from Windows.

And it made sense to me at the time when common screen resolutions were 640x480 or 800x600 or 1024x720, with average webpage widths keeping up with the accepted lowest common denominator of resolutions - less than 640, less than 800...

But as the average screen resolution in the mainstream grew beyond this point, especially with the transition to widescreen aspect ratios, webpage and document widths weren't keeping pace anymore because paragraphs of text become difficult to read after roughly 70 to 80 characters on a single line.

Maximizing a single document to fill a 1920x1200 would mean huge margins of whitespace, which is clearly a waste of screen real estate, which is why the zoom function in OS X I used to dislike has grown on me, as I do find myself frequently wanting to resize windows just enough to see the content before making room for another window on its side.

This is not to say that there won't be times that I'll still want to fill a window to the edges of the screen. Movies may have a full screen mode, but images in Photoshop or lines of code in an IDE are areas where that option would have utility.

User-Defined

Fit to Content

Maximized on a Modern Screen Resolution

Oddly, the pervasiveness of tabbed interfaces in recent years has meant more utility with wider windows, which goes against the grain of maintaining a limited width for readability in a document.

Oh, and if you're wondering what our conclusion was, we liked a third party application RightZoom for OS X, which provided the option to maintain a hybrid zoom/maximize function where one is accessible with an extra modifier key.

Thoughtfulness Zen of the Moment 3

Probably one of the underrated parts of the third generation iPhone (3GS) is its digital compass, which may evoke questions about its utility until a user actually uses it on the road. The potential utility of this compass gave me some excitement when I saw the iPhone GPS navigation app demo by TomTom the day the iPhone 3GS was announced, because it completed the last requirement necessary to make turn-by-turn GPS work seamlessly - your car's heading.

Now, with location-aware devices coupled with a map like Google Maps, it was already possible to navigate with steps of directions and your currently tracked location. But as anyone who has tried driving with any navigational aid knows, knowing the orientation of the streets grid relative to your direction is immensely more useful than driving with north fixed as upward.

Unfortunately, the TomTom GPS navigation app is not yet released, but one of the most accessible sample implementations right now is in the bundled Google Maps application, which cleverly displays heading in the form of car headlight beams. Moment of zen.

30 Favorite Usability Aspects and Features of Gmail

Five years ago, I finally received my invite to sign up for Google's new email service, Gmail. It was 2004, and I was loyal to Yahoo! Mail at the time for having the relatively cleanest UI and largest storage space (a whopping 6 megabytes) for a free major webmail provider.

There were plenty of gripes I had sent to the Yahoo! Mail feedback teams over the years - everything from the loss of free POP access since April 2002, to the extra step of having a forced home page before the inbox, to the little things like the promo tags appended to every outbound message ("Do you Yahoo!?" or one line ads for various services for Yahoo! or MSN in Hotmail).

Gmail addressed all of those, for free and immediately, and on top of that exhibited a friendly user interface and excellent usability. It seemed that everyone was falling head over heels over the 1 GB of space for a free webmail service, unheard of at the time, which was important too because with Yahoo! Mail at 6 MB and Hotmail at 2 MB, we were bound to be forced into deleting messages instead of keeping online archives. (This is largely why I no longer have my emails from 1998 in Yahoo! Mail or Hotmail.)

Ultimately, it's the little things that count, and Gmail was and remains the most well thought out webmail application out there. To celebrate my half decade as a happy user, here's a list of 30 reasons, one for every other month in the past five years, of what made me enamored with Gmail at its launch and thereafter. (There are more features than just these, but these were and are the ones that hold importance to me and won me over.)

1. threaded conversations
2. snippets previews of messages
3. labels (as opposed to folders, and color-coded) and advanced filters (and archive)
4. sending as custom address for outgoing messages
5. no promo tag lines appended to outbound messages
6. login goes straight to inbox, no home screen
7. no display ads, unobtrusive text ads
8. clickable textarea to reply in that part of the threaded conversation, without page reload
9. auto saving drafts as composing email
10. arrow indicators for which messages are directly to me, and which are mailing lists
11. search operators (is:unread, has:attachment)
12. attachments downloadable as a batch zip file with a folder
13. attachment previews for images and documents
14. single click to download attachment, instead of having to save as from browser
15. attachments upload in background as composing email
16. attachment upload progress bar
17. online viewing of documents via integration with google docs (doc, xls, ppt, pdf)
18. built-in chat (and later with AIM support and group chat)
19. server side chat logs (even when accessing via Jabber with clients or Meebo)
20. free POP access, including sent mail (later free IMAP, seamless with the labels)
21. POP fetching from other mail accounts
22. https
23. history details of IPs and method of access, and ability to sign off other sessions
24. notifications of live updates in threaded conversation while viewing/composing
25. unobtrusive confirmations/warnings as bars at the page top that gracefully disappear
26. mute conversations
27. google gears offline access
28. excellent spam filters (empirically far ahead of other webmail clients)
29. full css-based themes (as opposed to basic color switches), potential user contributions
30. drag-and-drop to move messages

It also had some behavioral side effects. I no longer used custom creative subject headers in replies, since we were maintaing RE: subject headers to keep messages organized in their appropriate threads. And because of their auto-reload of data and that they displayed the actual inbox count in the titlebar of the browser, I developed the habit of keeping my Gmail open, which made me spend far more time in webmail than ever before. This multiplied with built-in chat arrived in 2006 with sounds and flashing notifications. Meanwhile, the labels/filters/archives combined with the ability to send out as a different email address led to me sending and receiving all my Berkeley email through Gmail, and I soon expanded that to all my other email accounts until I had a central Gmail inbox with a vast collection of filters and labels doing all the sorting heavylifting for me. The GB+ of space also meant that I no longer had to delete email letters with large attachments, and could now keep all email online.

As a more or less loyal Yahoo! user from 1997 to 2004ish/2005, I anxiously waited for the invite-based Yahoo! Mail Beta and kept sending improvement requests such as #5, #6, and #9. Most of the requests I made never happened, and my invite arrived over a year after I had told all my contacts I had moved to my Gmail address. In contrast, #12 was one I sent to Gmail's feedback team, and maybe by coincidence, the feature appeared within a week. To give them the benefit of the doubt, they seemed like they were listening to their customers and were prolific with their continuous improvements of their product. It's worth noting that some of these were features at various points of Yahoo! Mail's heyday, such as #16 and the first part of #20. But as long as the Gmail team keeps this up, Gmail will remain the most useful and usable web application I've ever encountered in my online experiences.

The Global Inbox versus the Distinct Inboxes

When it comes to organizing multiple accounts on an email client, there are two major approaches - one is to send them all to a shared inbox, generally called a global inbox. How emails get filtered or sorted at that point varies, whether by folders or by labels. The other approach is to keep separate inboxes and sent/outbox/junk/trash folders for each mail account set up in the application.

Most desktop email clients offer the option of both inboxes global and separate, but it gets trickier with the constraints of the small viewports on mobile screens.

The way the iPhone OS has been doing it these past couple years seems to be consistent with the way the original iPods menus were done - you start a root level menu, and drill your way down (visually to the right) until you reach the level you wanted to visit. For example, on the original iPods, playing a song from the main screen involved: Music > Artists > Jack Johnson > All Songs > Upside Down, and going back (up one level) was done by the menu button (or the equivalent home button on the iPhone OS devices).

This was part of the foundation of the famed ease-of-use menu/clickwheel navigation of the iPods, and to the extent of the menu/home UI breadcrumbs, the iPhones and iPod touches. However, for tasks where switching quickly between two children-level items, heavily nested levels can hinder that. For example, one classic task is to switch between folders in two separate email accounts. From the first inbox, this requires going back two levels up emailone@someprovider.com > Accounts > emailtoo@someprovider.com > Inbox. That's four steps.



Now try this on the Palm Pre's webOS. For those maintaining separate inboxes, the accounts are listed in collapsed folder lists, so if both accounts's lists weren't expanded already, two taps for expanding both are required, after which both inboxes are just a scroll away from each other, and one tap for going back to the accounts list. If that's not enough, this mail client allows adding folders from various mail accounts into a global favorites list on the accounts list page, reducing even the need for a scroll.



The fact that there's a global inbox view while preserving the separate nature of the accounts ("All inboxes" on webOS) is a huge side perk, and actually excels beyond what many desktop applications offer. This is a shining example of a solid mail client implementation for both global/distinct inbox camps that scales well onto the mobile platform.