You are browsing the archive for Usability.

Quick tour of Gootodo

February 22, 2010 in Usability by Mark Hurst

Here’s a 3-minute tour of Gootodo.com, my online todo list. I’m working on a redesign, and this will soon go on the new homepage:

The Comprehensive Guide to Saving Images for the Web

February 22, 2010 in Usability by 8ify - usability

On the surface, saving images for the web can be a pretty straightforward process. However, if you dig deeper there’s a wealth of information and techniques you might be missing out on.

This article will focus primarily on the diverse features of Photoshop’s “Save for Web & Devices” command along with some best practices related to saving images that are optimized for web use. We’ll start extremely basic for all the beginners, but there will be plenty of advanced information for the seasoned veterans as we progress.

The Comprehensive Guide to Saving Images for the Web

Before the Save

Preparing images for the web doesn’t start at saving. It’s a good idea to check out a few things before you go into the Save for Web dialog.

First, you’ll want to have a look at your image mode. When designing for the web or any other on-screen media, you’ll want to make sure your images are formatted in RGB. Traditionally, CMYK is reserved for print. This is because there is a fundamental difference between creating colors with light vs. simulating colors with ink. While printers use tiny dots containing only one of four colors (Cyan, Magenta, Yellow or Black) to create the illusion of other colors, screens are capable of producing millions of colors.

Furthermore, RGB is an additive system, meaning the result of greater amounts of color is white. Conversely, CMYK is a subtractive system, meaning the lack of any color is white (the color of most paper) and colors are added to approach black. Additive systems are capable of producing much brighter colors across a wider spectrum.

The key information here is that for on-screen graphics, you can’t beat an RGB image.

Keep this in mind at the very start of a project, especially if you’re creating web graphics with Photoshop. Starting in an RGB workspace is far better than working with CMYK and converting later, which can create mottled gradients and muted colors. Photoshop’s Save for Web command will automatically convert CMYK images to the appropriate color system based on your choices in the dialog, but you’ll definitely want to know and consider the original color mode of the image before you even enter the dialog. If you don’t know the color mode of a given image, look in the menu bar under Image > Mode.

The second thing you’ll want to consider is the size of the original image. If your image is too large, hitting “Save for Web” will give you this warning:

The Comprehensive Guide to Saving Images for the Web

Essentially, Photoshop is telling you that your image is not only way too big for most web uses, but is also larger than the Save for Web command was created to handle. If you click “proceed” Photoshop will in fact go through with the save. However, the dialog and included commands can be painfully sluggish due to the size of the file, depending on your computer system resources. It’s a good idea to downsize large files before entering the Save for Web dialog to prevent any problems.

Entering the Save for Web Dialog

Once you have your color mode and image size all squared away, hit Cmd/Ctrl + Shift + Alt + S on your keyboard to bring up the Save for Web & Devices dialog.

Entering the Save for Web Dialog

If you’re not familiar with this dialog, it can look a bit overwhelming at first. In fact, even if you’re a time-tested Photoshop professional but don’t possess CS4, things are going to look a bit different as Adobe has completely redesigned this menu.

Everything in here is important, but you’ll find there are a few key features that you will use most often, highlighted below.

Entering the Save for Web Dialog

Image Size

In the bottom right of the window, you should see a section labeled “Image Size”. This section is pretty straightforward and works just like it did in previous versions of Photoshop.

Entering the Save for Web Dialog

You can choose to set the dimensions using either pixel height/width or by simply typing what percent of the original size you want your image to be. As you adjust these numbers, pay attention to your image preview as it will update to reflect the changes.

Resampling Quality

The most complicated part of this section is the Quality drop down menu. If you open it up, you’ll see that you have the choice of selecting Nearest Neighbor, Bilinear, Bicubic, Bicubic Smoother, or Bicubic Sharper. Each of these reflects a different method of pixel interpolation.

Resizing an image with only basic interpolation simply enlarges/reduces the pixel data and can produce some pretty ugly results. To prevent this, Photoshop attempts to manipulate the way the pixels are interpreted as the size of the image changes.

Unfortunately, there is no best solution for every image and Photoshop isn’t smart enough to decide which mode is best for a given image. By default, Bicubic is selected. This is generally good enough for most beginners and is in fact the most complex method. However, if you really want to learn to maximize your output, check out the brief explanations of the pros and cons of each method below.

Nearest Neighbor: This setting is the most basic interpolation mode and seeks to preserve the hard edges in an image by simply enlarging or reducing the pixel data as mentioned above. This may be good if your image doesn’t contain many gradients but will produce an over-aliased, pixelated image if you are significantly changing the size.

Bilinear: Slightly more intelligent than Nearest Neighbor and uses a weighted average of the 4 nearest pixels to increase the number of pixels. This method produces an anti-aliasing effect which eliminates harsh pixelated edges but can produce a blurry image as a result.

Bicubic: Bicubic is the most complicated method and samples from the nearest 16 pixels. As with bilinear, this method results in anti-aliasing to keep out any unwanted artifacts.

There are three versions of the Bicubic method in Photoshop: Bicubic, Bicubic Smoother and Bicubic Shaper. To get a hint for when to use each, we’ll look to another part of Photoshop. Close the Save for Web dialog and go the menu bar under Image > Size > Image Size. Now look under the “resample” dropdown menu and you’ll find some familiar options.

Entering the Save for Web Dialog

This time we see that each option (except Bilinear) comes with a little tip regarding when to use it. We can now see that each Bicubic option has a strength: Bicubic is best for creating smooth gradients, Bicubic Smoother is best for enlargement and Bicubic Sharper is best for reduction.

Always keep these tips in mind when resizing images within the Save for Web dialog. However, don’t blindly follow them without examining the results of each to decide which option is best for a particular image.

File Type and Image Quality

Near the top right of the window you’ll find the settings to choose which type of file you want to output along with various options pertaining to the quality of the output.

Entering the Save for Web Dialog

As you adjust these settings, you’ll obviously want to keep an eye on your image preview, but just as important as the way the image looks is the information directly under the preview pertaining to the image size and approximate load time.

Entering the Save for Web Dialog

Remember that there is always a trade-off between quality and file size. As a beginner, you may be tempted to choose quality over size and shoot for the maximum, but this is a big mistake that can cause your sites to load painfully slow. As you can see in the images above, by default my file size is coming in at nearly 1.3 MB. This is much larger than is preferable for most web images. With only a few size and quality adjustments, I can easily knock this down to around 20 KB (a much more preferable size).

File Type Options

There are three main file types we’ll want to focus on for saving images optimized for the web: GIF, JPG and PNG. Each file type has its own strengths and weaknesses and it is very important to know and keep these in mind when saving an image. We’ll start with the most complicated: GIF.

Entering the Save for Web Dialog

Working with GIFs

GIFs are popular for simple web-based graphics because of their relatively low file size. However, GIFs are restricted to a mere 256 colors and should therefore be used very selectively. Many designers will point out that photographs should not be saved as GIFs because of the millions of colors necessary to recreate a “real life” scene. This is definitely correct but does not give you the freedom to use a GIF on all non-photographic elements. For instance, the “six revisions” graphic that we’ve been using thus far was created in Photoshop and is therefore non-photographic, but it is still a very poor candidate for a GIF file. Check out the close up below of the text highlight using GIF compression:

Entering the Save for Web Dialog

As you can see, even with the highest number of colors enabled, the gradient from white out to red is pretty mottled. However, this definitely does not eliminate GIF as a useful file format. There are plenty of times when you’ll save an image such as a logo that may only have a few colors in it. Anything with large areas of solid color and very minimal gradients should look great as a GIF. For instance, if our image were changed to look more like the one below, we’d have a lot more freedom over which file type to use.

Entering the Save for Web Dialog

As you can see, the above image is fairly simple and shouldn’t even require the full 256 available colors. With GIF selected as the file type in the Save for Web dialog, you’ll have several options for how many colors you want to use ranging from 2 to 256.

Entering the Save for Web Dialog

Obviously, 2 colors is far too few to create a nice image. However, 256 looks a bit like overkill because our 16 color version is coming in so nice. This version comes it at a mere 7K while a JPG of similar quality would push us up to more than double that at 16K.

Other ways to reduce the file size of a GIF include reducing or eliminating any dither, adjusting the color palette settings (perceptual, adaptive, etc) and increasing the lossy compression. It would take at several more paragraphs to do these options justice so I’ll just encourage you to adjust these settings while watching the file quality and size to attempt to find an ideal result.

Working with JPGs

As I mentioned before, JPGs are going to be your best bet when working with photographs or graphics containing complex effects like shadows, gradients, etc. Because of the wide range of colors available in a JPG, you don’t have to worry about selecting a color palette. This just leaves the basic quality settings to adjust.

To adjust the image quality, either use the “Quality” slider on the right, or the present dropdown on the left (ranging from low to maximum). Again, remember to keep an eye of both your image preview and file size as you sample different settings. As you can see in the image below, there’s a wide gamut of quality between the lowest and highest settings.

Entering the Save for Web Dialog

Notice that as the quality decreases, it’s not just the hard edges that suffer but also the gradients as well. The graceful degradation from one color to another becomes a sloppy mess with clearly identifiable steps of color. However, at the largest size we’re pushing 90K, which is a bit unnecessary for this small image. You’ll find that the best solution is almost always somewhere between the lowest and highest settings. Try to find the lowest quality setting that doesn’t significantly degrade the finer visual details of your image.

Tip: By increasing the “Blur” option when saving a JPG, you can reduce file the size. However, only do this to the degree that it doesn’t significantly degrade the quality of your image.

Working with PNGs

Photoshop gives you two options when working with PNGs: PNG-8 and PNG-24. If you bring up the PNG-8 options, you’ll see that they are very similar to the options we saw for GIFs. Again we are back to choosing the number of colors up to a maximum of 256. This means that PNG-8 is limited to the same types of simple files that you would use for GIFs. Sometimes using a PNG-8 over a GIF can give you a smaller file size at a nearly identical quality. It’s best to experiment with both to see which provides a better result

PNG-24 on the other hand, provides a much higher quality image. PNG-24s retain much of the original PSD image quality and can handle transparency much better than a GIF.

Entering the Save for Web Dialog

As you can see in the image above, the shadow quality is fairly high and would look just fine dropped onto a solid background in an HTML file. However, there are two big downsides to using PNGs. The first is file size; notice that for the 550px wide PNG above the file size in 40.9K. This isn’t too bad for most modern internet connections but it’s a lot larger than an equivalent JPG or GIF and can really bog down a web page with a lot of images. The final and even more serious downside of using transparent PNGs is that they are not supported by all major web browsers. Nearly every professional web designer is aware of this and either ignores it in defiance of all users who won’t update their browsers, avoids using PNGs altogether, or comes up with clever hacks to trick browsers such as IE6 into submission. No matter which method you choose to live by, be sure to make an informed decision before leaving behind any visitors. If you already have a site, use Google Analytics or some equivalent to track the percentage of visitors you’re getting with browsers that don’t support PNGs. This allows you to make the best decision to cater to your current user base.

View Modes

By now you may be feeling a bit overwhelmed with the number of options available for saving images for the web. You might be thinking that switching between various options is too time intensive and that comparing those options accurately is nearly impossible without saving out a version of each. Fortunately, Photoshop eases these concerns by allowing you to see multiple options at the same time. In the top left corner of the Save for Web dialog, you’ll notice 4 tabs labeled Original, Optimized, 2-Up and 4-Up. These are often overlooked by designers but are extremely helpful in deciding on the optimized settings for a given image.

Original and Optimized

Viewing both the Original and Optimized tabs will give you a single image preview. The principal difference is that Original allows you to see the unaltered PSD while Optimized lets you see what the image will look like after it is saved with the current setting.

2-Up and 4-Up

These two tabs make saving images for the web a lot easier by allowing you to experiment with different options without losing settings. They both work exactly the same way and differ only in how many options you get to experiment with.

Entering the Save for Web Dialog

Entering the Save for Web Dialog

Each preview shows you the file type, size, quality and approximate loading time of the image with the settings pertaining to that selection. If you select a preview by clicking on it, you can change its settings on the right by using all of the methods discussed above. Then you can select another preview and change its settings for a quick visual comparison. You can compare across file types (JPG, PNG, GIF, etc) or within a given file type and limit the variation to quality settings. If you’re doing the latter, Photoshop can automate the task by automatically populating each window with a different setting so you can see which direction you want to go.

Entering the Save for Web Dialog

First select the type of file you think you’ll need, for instance: JPG. Then follow the picture above to locate the dropdown at the very top right of the Save for Web window. Click on this and go down to “Repopulate Views.” This will automatically fill each view with a JPG containing various quality settings. Just find the one with the most acceptable image clarity and file size and tweak the settings until you’re satisfied. This method makes it much easier for beginners to get a feel for the settings without spending a lot of time digging through them one at a time.

Working with Slices

Entering the Save for Web Dialog

Web designers that handle most of the initial layout in Photoshop usually work in one of two ways. They either pull images out of the layout and crop/save them individually, or they use Photoshop’s built-in slicing tools to select and save different parts of the image.

If you’re the type of designer that frequently use slices, there area a lot of options in the Save for Web dialog to speed up your workflow. Using the Slice Select Tool (C), found in the upper left, you can select individual slices to work with (hold shift to select multiple slices). Using this method, you can change the settings of each slice. This means if you want your header image to be a GIF but your footer to be a JPG, it’s as easy as selecting each slice and assigning a file type. After you’re done, hit the “Save” button to bring up the save dialog. Here you can decide if you want to save all the slices in your image as individual files or just those that you have selected. Exporting all slices at once allows you to accomplish the feat of collecting all the images you need from your PSD layout in a single step. This can save you loads of time if you’re working with a complex site design.

Outputting HTML

The final feature we’ll discuss is using the Save for Web dialog in conjunction with slices to output an actual HTML file. To begin, slice up your PSD and bring up the Save for Web dialog. After you get the settings you want for each slice, go back to that dropdown in the very top right of the window and click on “Edit Output Settings.”

Entering the Save for Web Dialog

This should bring up a window that gives you options to adjust the settings for HTML, Slices, Background, and Saving Files. Using these options you can adjust whether you want to output XHMTL, what color you want your background to be, what naming convention you want to use, etc. Most of these options are pretty straightforward and don’t require further explanation but I will recommend though that you select “Generate CSS” instead of “Generate Table” under the Slices menu. Unless you are actually trying to create a table, modern web standards discourage using tables to generate a web page layout.

Entering the Save for Web Dialog

Finally, to export your sliced PSD as an HTML document, hit “Save” and select the option to export “HTML and Images.” Don’t expect to use this method to build an entire website in Photoshop. It’s simply meant to aid the process of exporting the images and marking them up in HTML. If you do most of the layout in Photoshop anyway, using the export HTML option can save you a lot of time setting up the initial HTML file. The downside is that there will be plenty of clean up to do to organize the code in your preferred manner. Consequently, most seasoned coders will prefer to skip this method entirely and code from scratch, but I encourage you to experiment with it to see if you can improve your workflow in any way.

Conclusion

The information above is more than enough to start you on your way to becoming a Save for Web guru. I hope you’ve learned a thing or two you didn’t know about Photoshop’s “Save for Web & Devices” dialog. Use the comment section below to let us know what you thought of the article. Also, there’s actually still plenty more to the dialog that we didn’t go over so feel free to point out any features that you use regularly that weren’t mentioned above.

Related Content

About the Author

Joshua Johnson is a Graphic Designer/Web Design with over six years of experience working with a major international marketing agency. He is also the Editor of Design Shack, a web design and development blog. Check out his recent work and follow him on Twitter: @secondfret.

Rapid Desirability Testing: A Case Study

February 21, 2010 in Usability by 8ify - usability

By Michael Hawley Published: February 22, 2010
“There can often be disagreements among the members of a project team on which design direction we should choose.” In the design process we follow at my company, Mad*Pow Media Solutions, once we have defined the conceptual direction and content strategy for a given design and refined our design approach through user research and iterative usability testing, we start applying visual design. Generally, we take a key screen whose structure and functionality we have finalized—for example, a layout for a home page or a dashboard page—and explore three alternatives for visual style. These three alternative visual designs, or comps, include the same content, but reflect different choices for color palette and imagery. The idea is to present business owners and stakeholders with different visual design options from which they can choose. Sometimes there is a clear favorite among stakeholders or an option that makes the most sense from a brand perspective. However, there can often be disagreements among the members of a project team on which design direction we should choose. If we’ve done our job right, there are rationales for our various design decisions in the different comps, but even so, there may be disagreement about which rationale is most appropriate for the situation.

Free XHTML Template Pack: Classic Luxury

February 20, 2010 in Usability by 8ify - usability

Free XHTML Template Pack: Luxury Classic

Classic Luxury is a high quality, clean and simple CSS-based template with three custom pages created by CssTemplateHeaven exclusively for Six Revisions readers.

It is clean and has a lot of whitespace and nice typography. The code is well-organized and uses standards-based HTML and CSS.

Classic Luxury is great for portfolios and personal photo sites, and can be converted easily to a CMS theme as needed (such as Drupal or WordPress).

You may use this template in any projects you like (both personal/non-profit and commercial), but you cannot resell this pack’s source files.

Features

  • 3 custom page templates
  • Photoshop PSD files included
  • Valid XHTML
  • FancyBox support (jQuery plugin for modal windows)
  • Dropdown menus
  • Social media icons for Facebook, Twitter, and LinkedIn

Previews

Home

Luxury Classic

Gallery

Luxury Classic

Page

Page

Demo

Click below to open live demos of Classic Luxury’s page templates included in this pack.

Download

Related Content

About the Author

Dieter Schneider is the site owner of CssTemplateHeaven, where you can find high-quality CSS templates and WordPress themes (both premium and free). If you’d like to keep in touch with CssTemplateHeaven, you can follow them on Twitter: @csstemplates.

EverydayUX morsels (February 16th – February 19th)

February 19, 2010 in Usability by 8ify - usability

Packaging and the customer experience

February 19, 2010 in Usability by Mark Hurst

Fun with packaging. Which of these brands is truly trying to improve the customer experience?

• Cigarette makers change their packaging to satisfy a new law against selling “light” brands – but the colors of the packaging still signal the same old ruse: NYT story

• Campbell’s uses neuromarketing to create packaging that sells more cans of soup. They’re not actually improving the soup, just tweaking the packaging: WSJ story

• Tropicana halted a redesign of its orange juice packaging because it made the varieties much harder to distinguish: Khoi’s roundup (from 2009). See also Jamy Ian Swiss’s Gel Video which touched on the same topic.

• See also this post on Pirate’s Booty packaging.

Packaging is by definition a separate part of the experience from the product inside, be it poison, soup, orange juice, or snack chemicals. And to some extent the packaging has to use metaphor, or fantasy, perhaps even deception, to sell the product. But even deception can be a good thing (see Deception considered helpful). It all depends on what your longer-term aim is… or what the long-term effects of the product are.

“Ajax” is 5 years old today

February 18, 2010 in Usability by 8ify - usability

On February 18, 2005, Jesse posted his essay coining the term “Ajax” to explain a new breed of highly interactive web application. That concept took off like a rocket, and that page is still the single most viewed page on our site (it’s linked to from all the authoritative sources).

It’s been interesting to see how the term has been embraced over time. At this point, I’m just happy that I no longer see the phrase “Ajax-y goodness.”

I am curious — has the term “Ajax” affected you in some way over the past 5 years? How so? For us at Adaptive Path, it was key to our shift away from marketing communications websites towards interactive product development.

Design bugs out

February 18, 2010 in Usability by 8ify - usability

Hospital design The Design Council and the Department of Health partner to combat the spread of infection in U.K. hospitals. David Sokol reports in Metropolis Magazine.

“Patients go into hospitals to be cured of what ails them, but the ugly truth is that some get sick from being there. In 2007, around 9,000 people in the United Kingdom died from hospital-borne infections. Though the National Health Service has implemented procedural changes that have halved the number of antibiotic-resistant staph infections, or MRSAs, in the last three years, the agency is not content to stop there. [...]

In July 2008, the DH turned to the Design Council for solutions. The resulting program, called Design Bugs Out, began with a team conducting interviews for a month with patients and caregivers in NHS hospitals in Huddersfield, Manchester, and Southampton. From that research, health-care experts determined 11 categories of products in which redesigns could drastically reduce infection-related fatality rates.”

Read full story

Customer experience is harder than it looks

February 17, 2010 in Usability by Mark Hurst

I have to admit something strange: I’m amused by poorly designed websites. The worse the better. Much like some people “love to hate” movie villains, I get a peculiar satisfaction from finding myself completely lost in an ill-conceived, over-designed, steaming pile of a website.

And it happens all the time. With a few notable exceptions, almost any major site, brand, or company I visit online is at least mildly frustrating – and surprisingly often I find high-profile sites that are nearly impossible to use from the first page or two, leaving me astounded at the supreme waste of time and money they represent.

And I love to hate it – the juicy ridiculousness of it all – millions of dollars poured into something that is so obviously a wreck. I think I have to enjoy it on some level, given my role as a customer experience consultant; otherwise work would be pretty difficult (see also: doctors who can’t stand the sight of blood).

I’m guessing you’ve had a similar experience of being frustrated by a large company’s website. You go online to accomplish simple task X, or shop for product Y, or browse through information Z – and the site gives you swooping graphics and miniscule text from the designers, excited (not exciting) promotions from the marketing team, and features from the geeks that act as grand staircases to nowhere… but not the thing you were looking for.

At this moment, your reaction is probably similar to mine, those four well-known words: what were they thinking?!

The solution seems so simple. Why don’t these companies experience their website from the perspective of a user so that they can see what’s so obvious to us? If they’d just take an outside perspective, it would be easy for them to clean up the design, simplify the paths through the site, and generally orient their offering for the benefit of the user, rather than for short-sighted, self-serving aims. The company would save money in development and maintenance, and make more money from customers, and customers would be more likely to recommend the site to others. Slam dunk, case closed. Right?

I thought so at first. When I started Creative Good in 1997, offering to help companies do just this, I figured it would be an easy sale. After all, what company wouldn’t immediately see the value in listening to customers? Surely I could have an impact on enough major sites that users would generally have a less frustrating experience online by, say, the year 2000.

But a funny thing happened on the way to solving the problem: only a few companies paid attention. Instead… well, here’s an example. In one of my favorite stories from the early days, I found myself, in 1998, sitting in the office of a VP of Marketing for a top-20 website, pitching him the idea I described above: listen to users, make some simple changes, and start reaping the benefits immediately.

In the middle of my pitch I noticed he wasn’t paying attention. “Hey, look,” he said while still checking his computer screen, “our stock is up two points today.”

Needless to say, I didn’t get the job. The site never improved. And today, it’s no longer a significant player in its market.

It’s rarely that stark, though. In lots of cases my team or I have met an enthusiastic stakeholder within the company who buys into the customer experience idea, understands the problems on the site, and wants to improve. But they’re stymied by other parts of the organization who are affected by inertia, bureaucratic process, short-term thinking, turf wars, inefficiency and distraction due to information overload, and a host of other issues. There are often too many concerns inside the organization to properly focus on who’s outside the organization: the customers. And so the customer experience doesn’t improve, despite how obvious the need (and potential gain) may be to objective observers like you and me. Actually getting a change made is really hard.

About a year ago a talented young Web designer named Dustin Curtis posted a rant railing against American Airlines for its poor website design and suggesting a clean and attractive alternative. Mr. Curtis’s frustration – rage, really – came through in his letter, in which he “vowed never to fly your airline again.” All I could think was “ahh, youth.” It’s easy to find the problems out there but much, much harder to push through an improvement. Suggesting an improved design – as Curtis expertly did – is a tiny step in the process.

Maybe another time I’ll say more about how to make improvements to a customer experience. For now, let’s acknowledge that many, many high-profile websites are wasteful and way too difficult to use. And probably always will be. Let’s salute those people – inside and outside those companies – who are taking on the very difficult task of doing something about it.

- – -

See also:

The most important user experience method (written in 2003, still applicable today)

Creative Good (my company, 13 years old, still focused on improving customer experience)

Windows Phone: User Interface Teases & Transitions

February 17, 2010 in Usability by 8ify - usability

While the Windows Phone 7 Series user interface may not be optimized for high information resolution, it does make interesting use of teases and transitions as highlighted in the video below.

Because it is a touch-based device, the Windows Phone 7 Series uses a Natural User Interface (NUI) paradigm that turns actual content into interface controls. NUIs frequently need to let people know what elements are interactive. (Ideally everything is interactive in a touch-based UI but that’s a different point.) NUIs should encourage exploration and give people “permission” to touch things. Teasing people is one way of encouraging interactivity and exploration.

Teasing

The Windows Phone home screen teases people with a slight animation that hints at the content below the home screen image. As you can seen in the video above, the home screen images bounces when the phone starts revealing a bit of the options behind it. This encourages people to touch the surface and start using the device. Microsoft employs a similar design solution in Microsoft Surface with a water-like surface that encourages exploration. Contrast this teasing UI paradigm with the iPhone’s more literal “Slide to Unlock” welcome screen.

The Windows Phone also makes use of truncation throughout the user interface. Each of the main application screens include a tease of the content on the next screen over (as seen in the video above). This hint of additional content gives people a reason to move to the next screen and explore. The UI truncation is probably most pronounced in the application headers, which, in some cases span multiple screens.

Transitions

Transitions also help communicate interactions. When users move between screens, interaction components fly in or swivel highlighting the fact they are active and can be touched. Once someone taps on these components, they pivot or recede as if they were pushed backward into space. This animation (shown in the video above) reinforces the fact they are active.

Transitions are also used in the Windows Phone user interface to provide feedback when an action has been successfully completed. You can see this approach applied to comments and status updates (yep, in the video above).

One area of concern in the Windows Phone, however, is the quantity of different transitions present. It’s hard to get a sense of how consistently they are applied and if every animation is really necessary. There’s a lot of them! As Bill Scoot recently quoted: “It is vain to do with more what can be done with fewer (William of Occam circs 1323). Apply generously when using animation effects.”

Tags: mobile, windows, visualizations, interface, touch, microsoft