In the future I’d love to be able to comment & like photos from outside my iPhone. I’ve also noticed that the pull to refresh iphone gesture has now been ingrained in my multi-touch skill-set, so that would be nice as well. You can download Instagram for free at the App Store.

A few days after Steve Jobs announced the release of the iPad, I read that in Apple’s Reference Library: Preparing Your Web Content for iPad, and started to realize the drastic implications the evolution of multi-touch would have on interaction design. Anything we design for the web that requires a hover state has an uncertain future and could be subject to serious usability issues.

The Touch-Screen Boom

If you think this is something that can be addressed later, when multi-touch “catches on”, consider this: as of June 22, 2010 Apple has sold 3 million iPads in 80 days, 1.03 million touch screen phones are sold per day, and companies like Dell and HP have been developing & releasing touch interfaces for tablets and laptops for quite a while now.

The Hover Crutch

Hover states are everywhere. I don’t think I’ve ever written a stylesheet or designed a site without putting a significant amount of thought into how they should behave. As users, we’ve been conditioned to rely on hovers states to trigger changes in link color, reveal action items, and navigate through multiple tiers of a drop-down menu. Sliding our mouse pointers across a page to reveal hidden clickable points of action has become an automatic addition to our web browsing skill-set. As designers, we’ve turned to hover states to accommodate extra content and allow visual aesthetics to trump usability. Like it or not, those days are over and the interactions we design are going to have to stand on their own two feet.

I believe that in most cases, the best solution isn’t pursuing alternatives such as multi-touch hovering technology, trying to adapt hover-dependent designs, or transforming your website into an iPad/iPhone application. Instead of adding scripts, kilobytes, and billable hours to treat symptoms, I think the focus should be on simplicity and bullet-proof user experience design. In line with Luke Wroblewski’s statement that we should start designing for the web mobile-first, I propose that we should be designing for Multi-Touch first, and moving forward, we can only afford to add hover states as enhancements only.

Try to Avoid

• Hyperlinks that aren’t 100% obvious
• Javascript tooltips that show important information or metadata
• Displaying action items on hover. Examples I’ve seen typically involve edit / delete items.
• Displaying graphics in a less-than-ideal state until hovered: all those semi-opaque or black & white screenshots and photos that only display full color when covered by a cursor
• Drop-down menus. While some of these can be revealed on click or tap, be sure the user has cues that show those options.
• Focusing too much on hover dependent CSS3. I know it’s a bit of a heartbreaker, but while these have always been seen as enhancements, we’re going to have to settle with the fact that multi-touch users won’t be seeing our fancy transitions.

How do we adapt?

More often than not, making adjustments won’t be a quick or a simple process. The more layers of interaction a site has, the more work is going to have to be done to address usability issues. I’ve noticed that a few of my favorite sites have already taken a variety of steps to provide some fixes.

Show everything.

Prioritize your content, and if you’ve been hiding things behind hover states, make room to display them. The WordPress admin posts screen is a great example of this. Normally, action items are only visible on hover, but if you login with a touch device the links are always displayed.

Utilize tap to reveal a hover state.

Depending upon the implementation, this can be risky; Amazon has done fairly well with this method for their category-based shopping navigation. The paneled list and orange arrows help to make those areas clearly tappable. Another example can be found in Basecamp’s edit and delete controls for to-do lists, milestones, and files. When you hover over one of these the action items appear. For touch-screens they’ve built a javascript popup that works fairly well once you’ve figured it out. The problem is that users get no cue that tapping the to-do text is even an option, and I can’t help but think a solution similar to WordPress would have worked better. That being said, I’d happily pay a few extra pennies per month to get a mobile version of Basecamp.

Build specifically for touch-screen devices

and take advantage of native device controls, gestures and popovers. Touch-screen apps for Twitter and Gowalla play a key role in their overall success and are probably used more than the websites themselves. I use the Netflix iPad app regularly, but in many cases it feels like a hover-dependent website dropped into an iPad viewport. Currently, if you’re browsing instant titles and want to add something to your queue by tapping, you’re looking at a 3 step series of taps instead of an instant hover reveal option with a point-and-click interface. If you’re going to build specifically for touch, you’ve got to follow through.

Wait for touch hover technology.

I’m not convinced this would do anyone any good. It may be exciting to see what Cypress has come up with, and to know that Apple has applied for a patent for a proximity sensing touch-screen, but this does worry me. I’d hate to see us revert to our old shortcuts and make user experience sacrifices just because the technology is in place. Plus, we’re going to look like a bunch of idiots who are afraid to touch our smart phones & iPads. On the bright side, Phil Dunphy would love it!

We’re going to be OK.

Ultimately, I think seeing hover states fade away will make the web a better place. There never has been any substitute for concise content, clear interaction, and simple design. If we focus on core elements that make browsing the web great, our sites will function properly no matter how people use them.

@font-face usage has been fortified by services like Typekit & Fontdeck, CSS3 & HTML5 are popping up everywhere, and with the release of the iPad, multi-touch technology is drastically changing web design.  My goal has been to cut out the extra divs, widgets and doodads so browsing is more fun for you and posting is less work for me.

There’s nothing on that plate but gristle & fat!

I wanted to start by clearing out all the non-essentials.  Any elements that weighed down the markup, design or user experience from the previous version had to go.  I scaled back the footer by removing the black content box, list of posts and tweets.  The Comments section was updated by trading the author comments in the margin and indented threads for a good ol’ fashioned list with @replies.  I 86-ed the 1px horizontal lines filling the page margins.  Though they did frame the page nicely, they cramped art-directed posts’ style,  and the same effect can be achieved with well-placed text and line-height.

Inspired by Multi-Touch

This site wasn’t intended solely for the iPad, though it is inspired by my experience browsing the web sans mouse.  Many of the assertions I made before getting an iPad have been strengthened each time I slide, swipe and tap my way across the inter-web.  Each change I’ve made (larger font size, less content/page, fewer columns) has been shaped by my belief that the future of web design lies in making browsing all play and no work.  Hunching over a keyboard at a desk and squinting at an overstuffed page with 12px font is work you don’t get paid to do, so why do it?

A New Mark

I knew I wanted to move away from Helvetica as the typeface for the body copy as well as for my logo.  I thought the mark needed a hand-drawn look to offset all the obsessive pixel pushing I was bound to do while designing. Fortunately, Reagan Ray was willing to bring custom lettering talent to the process.  After trading a few ideas, Reagan took to sketching and then ran a few lettering options through Illustrator.  I immediately gravitated towards this script version, dropped it in a black circle and let it set the tone for the rest of the site design.  More than anything, my favorite thing about the new mark is that Reagan did it.  I dig his style... always have and always will.

The Design Process

Once I had the new mark & simplified content list I set out to experiment with design, mainly consisting of 30 minute design sessions where I’d try different combinations of fonts, font sizes, page widths and line heights which were checked with fresh eyes at regular intervals during the day, using both a point-and-click interface and the iPad.  After a couple of weeks, I settled on a 1000px wide site with a 23px baseline grid for the text.

Updated Typography Served Up Via Typekit

For the body copy, I went back and forth between a 14, 16 and 18px font size.  14 seemed small when zoomed out on a touch device, but 18 seemed excessive on my laptop, especially when you consider how large heading fonts would need to be to maintain visual hierarchy.  So, 16px Georgia it was until I found FF Meta Serif via Typekit.  I love this typeface and think it interacts well with the new mark.  I also enjoy using Typekit & believe that they’re doing important work for both the web and type communities.

The Code-out

The markup & WordPressing process was aided by Nathan Staines’ HTML5 adaptation of Elliot Jay Stocks’ Starkers theme.  In addition, CSS3 came in handy in quite a few cases.  Whenever possible, I gladly trade larger javascript files or semi-transparent pngs for a single line of progressively enriched CSS code.  The search page uses -column-count and column-gap to set the tags into columns, and I use rgba color to set the 1px lines on the header and footer.  I also threw in 0.2 second ease-out transitions for the link hovers. With the help and council of Paravel’s Development Sensei, Dave Rupert, I was able to minimize file size and load times by running images through ImageOptim, making icon sprites and installing WP Super Cache.

Content Navigation

I had 3 times the content to work with this round and saw a real need for a good search page and tags system, which were added to the main navigation.  While I enjoyed displaying those billboard style banners on the Articles page, it became progressively harder to find older posts.  Now the layout mimics the notes page, but with post-style referencing thumbnails.  I also added a more prominent Previous & Next navigation for easy browsing. I sure hope you enjoy the updated site.  Let me know what you think.

Click here to download the 1024px x 1024px wallpaper.

Shaun is now tumbling the innovation at blog.mimeoverse.com. Check it out and save your pennies for what I think will be an epic multi-touch game.

For years, web designers have been working within a firmly established jig. Books have been published, studies have been conducted and businesses have been built on a handful of fundamental interface design principles. Many of these rules have been written based on the understanding that a mouse will be serving as the primary tool in carrying out the user’s will. What happens if this lowest common denominator for user interface design is replaced with a finger tip? Multi-touch technology will soon change the web more CSS3 or even HTML5.

Mouse Clicks VS Finger Tips

If I squint, I can get my mouse pointer accurate down to a single pixel. The tip of my right index finger measures 30px X 40px. That makes my finger 1200 times less precise than my mouse pointer. Does that mean that multi-touch technology is a step backwards? No. After all, user interface design is all about making things easier and more natural. Multi-touch does this by removing the middle man, in this case a mouse & cursor. Any gripe people have with multi-touch as it grows won’t be because they miss carefully positioning a mouse pointer to click a link. It will be because web designers have crammed too much on a page, or made link buttons too small for fingers to easily tap.

Scrolling VS Zooming & Tapping

Until now, websites have moved vertically, like a filmstrip, through a browser window. This specific linear method of engaging content has made a web designer’s job relatively easy. Counting on the fact that users are limited to scrolling from top to bottom while viewing the entire width of the page, important items can be placed at the top of the page (above the fold) while additional content can be arrayed below, or in a sidebar. With multi-touch, DIVs are the new fold. Being able to tap on a section to zoom in will allow users to focus only on the content they want to see. This quadrant based page browsing will make skipping over uninteresting content & advertisements much easier.

Multi-touch VS Mobile VS Standard

These are two very different areas of interface design that have a lot in common. Many of my iPhone apps already cater to finger tips with their big buttons & super simple navigation. So this begs the question, do we need to design a mobile and a multi-touch version of a website? I don’t think so. I think the core structure of what the regular version of a website will need to adapt to fit fingertips, which means everything will have to be redone, re-imagined... re-figured out.

A Change in Posture

During the Apple Keynote, Steve Jobs wasn’t hunched over a desk pecking characters into a keyboard. He was sitting on a couch, casually flipping through content on his iPad. To an extent, web design has been all about what we want users to see and when. We’ve been orchestrating the user-experience from click in to click out. With multi-touch the tables have turned. With a brand new set of gestures, users will be calling the shots as they tap, swipe, pinch and zoom. It will now be up to the web design community to study up & do their best to follow along.