<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;User Interface</title>	<link>http://tc.eserver.org/dir/Articles/User-Interface</link>
	<description>A listing of the most recently indexed works about Articles and User Interface in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Articles&gt;User Interface</title>
		<link>http://tc.eserver.org/dir/Articles/User-Interface</link>
	</image>
	<item>
		<title>The Ever-Evolving Arrow: Universal Control Symbol</title>
		<link>http://tc.eserver.org/35655.html</link>
		<guid>http://tc.eserver.org/35655.html</guid>
		<description>The arrow and its brethren are everywhere on our computer screens. For example, a quick examination of the Firefox 3.0 browser, shown in Figure 1 in its standard configuration, yields eight examples of arrows—Forward, Back, and Reload buttons, scroll bar controls, and drop-down menus that reveal search engine, history, and bookmark choices.</description>
	</item>
	<item>
		<title>The Consistency Conundrum</title>
		<link>http://tc.eserver.org/35597.html</link>
		<guid>http://tc.eserver.org/35597.html</guid>
		<description>A common mandate at many software companies is “Make our products consistent!”   I’ve heard this clarion call for consistency at every company I’ve worked for that has more than a single product or service.  The rationale behind the consistency mandate is that it will reduce design and development costs, improve the overall quality of the software, strengthen the brand (“the products should all look like they come from the same company”), make learning easier for users, and reduce errors when multiple products are used together.  These are all great goals, but there is a problem with the consistency mandate – consistency is complex, multi-dimensional, and sometimes at odds with other important goals like usability.</description>
	</item>
	<item>
		<title>The Road to XAML</title>
		<link>http://tc.eserver.org/35606.html</link>
		<guid>http://tc.eserver.org/35606.html</guid>
		<description>XAML stands for eXtensible Application Markup Language and was created by Microsoft. It is currently the primary mechanism for declaratively creating the user interface in a Windows Presentation Foundation (WPF) application.  WPF is part of the .NET 3.0 framework. Why discuss these very technical things in a design blog post? The answer is simple: because XAML is designed for designers. It has other uses of course, but one of its main tenets is that XAML enables the separation of UI and logic (code).&#xD;&#xD;That is a very powerful concept! In this and future posts, I will explain how a few of us at Autodesk are using XAML in our design process as a way to enable design refinement during the Development phase.</description>
	</item>
	<item>
		<title>Preferences Considered Harmful</title>
		<link>http://tc.eserver.org/35573.html</link>
		<guid>http://tc.eserver.org/35573.html</guid>
		<description>Every programmer and user interface designer eventually comes to this point: You can’t decide how a specific part of your user interface should behave. It’s easy, of course. Just make it a preference, and everyone will be happy.</description>
	</item>
	<item>
		<title>Touchscreen Usability</title>
		<link>http://tc.eserver.org/35574.html</link>
		<guid>http://tc.eserver.org/35574.html</guid>
		<description>Touchscreen devices can only work well if both hardware and software are uniquely optimized for touch interaction. Simply adding touch interaction to an existing device will make the user experience worse instead of better.</description>
	</item>
	<item>
		<title>Treating User Myopia</title>
		<link>http://tc.eserver.org/35577.html</link>
		<guid>http://tc.eserver.org/35577.html</guid>
		<description>Fortunately, you don&apos;t see dialogs in web apps much, but this sort of modal dialog lunacy is, sadly, becoming more popular in today&apos;s AJAX-y world of web 2.5. Those who can&apos;t learn from history are doomed to repeat it, I guess.</description>
	</item>
	<item>
		<title>Teaching Users to Read</title>
		<link>http://tc.eserver.org/35578.html</link>
		<guid>http://tc.eserver.org/35578.html</guid>
		<description>This may sound a little harsh, but you&apos;ll see, when you do usability tests, that there are quite a few users who simply do not read words that you put on the screen. If you pop up an error box of any sort, they simply will not read it.</description>
	</item>
	<item>
		<title>Bringing Gaming to the Disabled</title>
		<link>http://tc.eserver.org/35387.html</link>
		<guid>http://tc.eserver.org/35387.html</guid>
		<description>To a huge number of gamers and would-be gamers, though, even the most sensible and well-laid-out controller scheme is unplayable. For them, accessibility and interface issues make gaming at best an incomplete experience and at worst a total impossibility.</description>
	</item>
	<item>
		<title>Powers of 10: Time Scales in User Experience</title>
		<link>http://tc.eserver.org/35307.html</link>
		<guid>http://tc.eserver.org/35307.html</guid>
		<description>From 0.1 seconds to 10 years or more, user interface design has many different timeframes, and each has its own particular usability issues.</description>
	</item>
	<item>
		<title>Enhancing User Interaction With First Person User Interface</title>
		<link>http://tc.eserver.org/35216.html</link>
		<guid>http://tc.eserver.org/35216.html</guid>
		<description>First person user interfaces can be a good fit for applications that allow people to navigate the real world, “augment” their immediate surroundings with relevant information, and interact with objects or people directly around them.</description>
	</item>
	<item>
		<title>A Review of the Balsamiq Mockups wireframing application</title>
		<link>http://tc.eserver.org/35206.html</link>
		<guid>http://tc.eserver.org/35206.html</guid>
		<description>This is a review for Balsamiq Mockups. This is a reasonably-priced application for creating wireframes that is easy to learn and use suitable for smaller projects. Creating interactive prototypes out of Balsamiq wireframes is now possible with the release of another application called Napkee. This review talks talks about: Balsamiq Mockup specifications; Balsamiq’s distinct visual character and how it work both in favor and against Balsamiq being adopted by users; Pros and cons of the application; and a conclusion with a recommendation on who should use and what to use Balsamiq Mockups for.</description>
	</item>
	<item>
		<title>User Interface Pattern Documentation Review</title>
		<link>http://tc.eserver.org/35179.html</link>
		<guid>http://tc.eserver.org/35179.html</guid>
		<description>User interface (UI) patterns have the potential to make software development more efficient. The prospect of such efficiency gains has led to interest in user interface (UI) patterns by individuals and organizations looking for ways to increase quality while at the same time reducing the costs associated with software development.</description>
	</item>
	<item>
		<title>The Inclusion Principle</title>
		<link>http://tc.eserver.org/35173.html</link>
		<guid>http://tc.eserver.org/35173.html</guid>
		<description>Affordance allows us to look at something and intuitively understand how to interact with it. For example, when we see a small button next to a door, we know we should push it with a finger. Convention tells us it will make a sound, notifying the homeowner that someone is at the door. This concept transfers to the virtual environment: when we see a 3D-shaped button on a web page, we understand that we are supposed to “push” it with a mouse-click.</description>
	</item>
	<item>
		<title>Inside Out: Interaction Design for Augmented Reality</title>
		<link>http://tc.eserver.org/35101.html</link>
		<guid>http://tc.eserver.org/35101.html</guid>
		<description>While ubiquitous computing remains an unpleasant mouthful of techno-babble to most people who know the term, and everyware is still an essentially unknown idea, the visibility of augmented reality has surged in the last twelve months.</description>
	</item>
	<item>
		<title>Systems Thinking: A Product Is More Than the Product</title>
		<link>http://tc.eserver.org/35092.html</link>
		<guid>http://tc.eserver.org/35092.html</guid>
		<description>A product is actually a service. Although the designer, manufacturer, distributer, and seller may think it is a product, to the buyer, it offers a valuable service. In reality a product is all about the experience.</description>
	</item>
	<item>
		<title>The Art of Icons</title>
		<link>http://tc.eserver.org/34935.html</link>
		<guid>http://tc.eserver.org/34935.html</guid>
		<description>Being &quot;minimalist&quot; and &quot;streamlined&quot; is not always most effective. Have you ever written yourself a quick, shorthand note, only to find later that you had no way to unpack your own great idea?&#xD;&#xD;Icons work similarly. They are pictures – meant to provide a visual shorthand to users moving through a task. While research indicates that icons are best when initially paired with text to increase recognition and learnability, users experienced with a given set of icons will begin to ignore the text, scanning for and acting from the image alone.</description>
	</item>
	<item>
		<title>Search Goal Redefinition Through User-System Interaction</title>
		<link>http://tc.eserver.org/34969.html</link>
		<guid>http://tc.eserver.org/34969.html</guid>
		<description>The purpose of this research is to examine search goal redefinition during users&apos; interaction with information retrieval systems.</description>
	</item>
	<item>
		<title>情報アーキテクチャの間違いトップ10</title>
		<link>http://tc.eserver.org/34903.html</link>
		<guid>http://tc.eserver.org/34903.html</guid>
		<description>ウェブサイトは、その構造とナビゲーションシステムとが互いに支え合っていなければならない。検索システムとも結びついていなければならない。サブサイトに至るまで一体化していなければならない。複雑で、一貫性が無く、選択肢が隠れていて、UIが扱いにくければ、ユーザーは必要なものを見つけられない。 </description>
	</item>
	<item>
		<title>The Worst Interface Ever</title>
		<link>http://tc.eserver.org/34871.html</link>
		<guid>http://tc.eserver.org/34871.html</guid>
		<description>Never, ever, ever let systems-level engineers do human interaction design unless they have displayed a proven secondary talent in that area.</description>
	</item>
	<item>
		<title>Using Wikis to Document UI Specifications</title>
		<link>http://tc.eserver.org/34751.html</link>
		<guid>http://tc.eserver.org/34751.html</guid>
		<description>As Agile gains momentum as a development approach of choice, documenting design becomes a challenge. Peter Gremett shows how using a wiki to capture your design is a great way to be adaptive as you build and deliver product to customers.</description>
	</item>
	<item>
		<title>Reusing the User Experience</title>
		<link>http://tc.eserver.org/34645.html</link>
		<guid>http://tc.eserver.org/34645.html</guid>
		<description>As a rule of thumb, the earlier in the development process reuse can occur, the more efficient reuse becomes. Like software component reuse, the reuse of UX design elements can be a very efficient form of reuse—particularly because this form of reuse occurs very early in the product development cycle. The ability to reuse prior work effectively is one characteristic of a mature discipline.</description>
	</item>
	<item>
		<title>Great Designs Should Be Experienced and Not Seen</title>
		<link>http://tc.eserver.org/34563.html</link>
		<guid>http://tc.eserver.org/34563.html</guid>
		<description>When things are going well in a design, we don&apos;t pay attention to them. We only pay attention to things that bother us. The same is true with online designs. We attend to things that aren&apos;t working far more than we attend to things that are. When the online experience frustrates us, we pay attention to its details, often because we&apos;re trying to figure out some way to outsmart it.</description>
	</item>
	<item>
		<title>What Makes a Good Mobile Interface?</title>
		<link>http://tc.eserver.org/34546.html</link>
		<guid>http://tc.eserver.org/34546.html</guid>
		<description>While the perfect mobile user interface is beast that doesn&apos;t exist, there are good interfaces that work around any issues there are with the displays on mobile devices.</description>
	</item>
	<item>
		<title>Top-Ten Information Architecture (IA) Mistakes</title>
		<link>http://tc.eserver.org/34539.html</link>
		<guid>http://tc.eserver.org/34539.html</guid>
		<description>Structure and navigation must support each other and integrate with search and across subsites. Complexity, inconsistency, hidden options, and clumsy UI mechanics prevent users from finding what they need.</description>
	</item>
	<item>
		<title>Usability Tips for Your Application (Part I)</title>
		<link>http://tc.eserver.org/34514.html</link>
		<guid>http://tc.eserver.org/34514.html</guid>
		<description>There are a exponentially growing amount of applications being developed. Some of them vanish at an early stage, while others grow to be quite (and sometimes extremely) popular. What really dazzles me is how sucky many of them (both the popular and the unpopular ones) are regarding how they deal with user-interaction.</description>
	</item>
	<item>
		<title>How to Improve the UI--Really!</title>
		<link>http://tc.eserver.org/34446.html</link>
		<guid>http://tc.eserver.org/34446.html</guid>
		<description>A colleague has made me realize that user assistance writers are codependents of bad UI design. Because we explain how the UI really works, we somehow leave our developers and companies feeling like they&apos;re &quot;covered&quot; when the users have a bad experience.</description>
	</item>
	<item>
		<title>Refreshable Braille and the Web</title>
		<link>http://tc.eserver.org/34428.html</link>
		<guid>http://tc.eserver.org/34428.html</guid>
		<description>Many people have not had the opportunity to see someone use a refreshable Braille device to access the web. I recently videoed Bruce Maguire describing how he uses the Internet with a refreshable Braille display. He also demonstrates finding a book on the Amazon site. Transcript of the video is at the end of this document.</description>
	</item>
	<item>
		<title>Using Verbs As Nouns in User Interfaces</title>
		<link>http://tc.eserver.org/34408.html</link>
		<guid>http://tc.eserver.org/34408.html</guid>
		<description>To better manage interactions with such large datasets, we’ve incorporated the concept of views, in the same way that Microsoft Outlook and SQL Builder use them. However, my initial usability testing has found that the concept of views is escaping most people, and I think it often boils down to the term itself. Even if I show users what the software does—and they pretty much always like it when they see it—they still often cannot get over the initial hurdle of the naming convention.</description>
	</item>
	<item>
		<title>Operating System Interface Design Between 1981-2009</title>
		<link>http://tc.eserver.org/34320.html</link>
		<guid>http://tc.eserver.org/34320.html</guid>
		<description>Over the years a range of GUI’s have been developed for different operating systems such as OS/2, Macintosh, Windowsamiga, Linux, Symbian OS, and more.&#xD;&#xD;We’ll be taking a look at the evolution of the interface designs of the major operating systems since the 80’s.</description>
	</item>
	<item>
		<title>On User Interface Design, Part I</title>
		<link>http://tc.eserver.org/34171.html</link>
		<guid>http://tc.eserver.org/34171.html</guid>
		<description>The first of a pair of presentations by Alan Kay (of Smalltalk fame). The presentation is from 1983 and discusses the development of user interface design from the 1960s onward.</description>
	</item>
	<item>
		<title>On User Interface Design, Part II</title>
		<link>http://tc.eserver.org/34172.html</link>
		<guid>http://tc.eserver.org/34172.html</guid>
		<description>The second of a pair of presentations by Alan Kay (of Smalltalk fame). The presentation is from 1983 and discusses the development of user interface design from the 1960s onward.</description>
	</item>
	<item>
		<title>Including Recommendations in User Interfaces to Enhance Motivation</title>
		<link>http://tc.eserver.org/34097.html</link>
		<guid>http://tc.eserver.org/34097.html</guid>
		<description>Motivation is an important factor in any kind of online interaction or transaction. People need a little encouragement when they’re not really convinced they should take any action or are uncertain about what action to take next. As users perform tasks online, they need to understand what’s happening and expect you to help them move forward. This article discusses the responsibility of a user interface to provide recommendations along a user’s path of interaction.</description>
	</item>
	<item>
		<title>Putting the Wrecking Ball to the User Interface (UI)</title>
		<link>http://tc.eserver.org/34065.html</link>
		<guid>http://tc.eserver.org/34065.html</guid>
		<description>Does a truly intuitive user interface exist? The author of this blog post doesn&apos;t think so. To create one, designers and developers really need to put the wrecking ball to the UI as it is now.</description>
	</item>
	<item>
		<title>Reviewing User Interfaces</title>
		<link>http://tc.eserver.org/33954.html</link>
		<guid>http://tc.eserver.org/33954.html</guid>
		<description>While user interface (UI) reviews often occur at the end of the development cycle, I recommend that you get involved early in the process, preferably when the designers create the initial wireframes or paper prototypes. Why? Making changes early in the process reduces development costs. Plus, if you identify usability issues early, it’s much more likely the team can remedy them before launch, preventing bad reviews.</description>
	</item>
	<item>
		<title>Making the Right Constraints for Usable and Accessible User Interfaces</title>
		<link>http://tc.eserver.org/33840.html</link>
		<guid>http://tc.eserver.org/33840.html</guid>
		<description>This paper focuses on managing constraints in a way that enables developers to create an accessible and usable user interface (UI). The constraining processes presented in this paper comprise of a language to describe a logical web page in an application, a basic bottom-up repository management system and the processing required for compiling pages.</description>
	</item>
	<item>
		<title>Antipatterns</title>
		<link>http://tc.eserver.org/33720.html</link>
		<guid>http://tc.eserver.org/33720.html</guid>
		<description>Using patterns has become a well-known design practice and is also considered best practice in the software development community. While UX teams can and should constantly promote best practice, we can also approach tackling poor design practice from the other side: antipatterns. Antipatterns are approaches to common problems that might appear obvious, but are less than optimal in practice.</description>
	</item>
	<item>
		<title>Text Treatment and the User Interface</title>
		<link>http://tc.eserver.org/33723.html</link>
		<guid>http://tc.eserver.org/33723.html</guid>
		<description>Before graphic user interfaces, text was the primary means of both input and output defining human-computer interactions. Even today, much of the information user interfaces present is textual. Therefore, we should not underestimate how the right text treatment can measurably improve user productivity and increase user satisfaction. As new technologies become available—for example, larger monitors with higher resolutions—a good foundation of knowledge about effective text treatment can help designers create usable user interfaces for them more quickly.</description>
	</item>
	<item>
		<title>Usability in Practice: The Human Face Of Software</title>
		<link>http://tc.eserver.org/33590.html</link>
		<guid>http://tc.eserver.org/33590.html</guid>
		<description>Welcome to Usability In Practice. This is the first in a series of columns that will focus on the design of the user experience (UX). In the past, user experience was not a high priority for most development projects, but that&apos;s changed. Today, end users have a lot of experience with the Web and with software. They want design that&apos;s easy to learn and use and that fits their workflow. This column will show you how to deliver such designs.</description>
	</item>
	<item>
		<title>Intuitiveness and Adaptability</title>
		<link>http://tc.eserver.org/33495.html</link>
		<guid>http://tc.eserver.org/33495.html</guid>
		<description>With few exceptions, intuitive user interfaces really don&apos;t exist. Familiar interfaces do, however. But does that mean developers need to be locked into the same old design patterns? There&apos;s no reason why they should.</description>
	</item>
	<item>
		<title>Create the World, The Interface Will Follow</title>
		<link>http://tc.eserver.org/33485.html</link>
		<guid>http://tc.eserver.org/33485.html</guid>
		<description>In user experience design, there is a growing emphasis on starting projects by creating robust descriptions of the prospective users. Through contextual inquiry and persona development we gain insight into people’s needs; ascertain their desires; and illuminate their behavior, wishes, hopes and dreams. But in an attempt to create archetypal descriptions of people, the specificity of the environments people inhabit are often times diminished—research is conducted across broad cross-sections of markets to ensure that common experiences are identified and explored.</description>
	</item>
	<item>
		<title>Jensen Harris Tells Dan About Microsoft Office&apos;s Ribbon Interface</title>
		<link>http://tc.eserver.org/33486.html</link>
		<guid>http://tc.eserver.org/33486.html</guid>
		<description>Dan Harrelson, design technologist at Adaptive Path, recently spoke with Jensen Harris, Group Program Manager of Microsoft’s Office User Experience team. Jensen was one of the key designers behind the new Ribbon user interface introduced in Office 2007. Dan and Jensen chatted about Office’s redesign and the techniques he uses to keep the focus on user needs within an organization the size of Microsoft.</description>
	</item>
	<item>
		<title>Interaction Elasticity</title>
		<link>http://tc.eserver.org/33453.html</link>
		<guid>http://tc.eserver.org/33453.html</guid>
		<description>Usage goes down as interaction costs increase. User motivation determines how fast demand drops, following an elasticity curve.</description>
	</item>
	<item>
		<title>Year&apos;s 10 Best Application User Interfaces</title>
		<link>http://tc.eserver.org/33461.html</link>
		<guid>http://tc.eserver.org/33461.html</guid>
		<description>Many winners employ dashboards to give users a single overview of complex information and use lightboxes to ensure that users notice dialogs. Also, the Office 2007 ribbon showed surprisingly strong early adoption.</description>
	</item>
	<item>
		<title>Polite Computers Win Users&apos; Hearts and Minds</title>
		<link>http://tc.eserver.org/33467.html</link>
		<guid>http://tc.eserver.org/33467.html</guid>
		<description>Computer glitches would be a lot less annoying if the machines were programmed to acknowledge errors gracefully when something goes wrong, instead of merely flashing up a brusque &quot;you goofed&quot; message.</description>
	</item>
	<item>
		<title>Could You Repeat That in English?</title>
		<link>http://tc.eserver.org/33468.html</link>
		<guid>http://tc.eserver.org/33468.html</guid>
		<description>Frequently, error messages are totally uninformative -- or, worse, just plain wrong. Here, we look at how meaningful error messages can make it easier for users to correct problems without having to rely on technical support, and how poorly chosen messages can turn users into ex-users.</description>
	</item>
	<item>
		<title>The Human Factors of Touch Input Devices</title>
		<link>http://tc.eserver.org/33469.html</link>
		<guid>http://tc.eserver.org/33469.html</guid>
		<description>The popularity of touch input devices for use in a wide variety of information, telecommunication, and other systems applications warrants a review of the role of human factors in the design and use of these devices, particularly touch screens and touch pads. This report reviews empirical research into the human interface design issues of touch input devices including display mounting angle, touch biases, touch area size and shape, feedback, and touch key interaction strategies. The limitations and capabilities of the devices for supporting a variety of tasks are examined as are comparisons between these devices and more conventional input devices such as keyboards. Attempts to improve the user interaction with these devices are also reviewed. Conclusions and recommendations regarding the use and design of touch input devices are provided.</description>
	</item>
	<item>
		<title>AJAX Interface Design</title>
		<link>http://tc.eserver.org/33384.html</link>
		<guid>http://tc.eserver.org/33384.html</guid>
		<description>AJAX enables faster, more responsive Web applications through a combination of asynchronous Javascript, the Document Object Model (DOM), and XMLhttpRequest. What this means for Web interface designers is that a DHTML-based Web application can make quick, incremental updates to a user interface without reloading the entire screen.</description>
	</item>
	<item>
		<title>The Art of Expectations</title>
		<link>http://tc.eserver.org/33371.html</link>
		<guid>http://tc.eserver.org/33371.html</guid>
		<description>I’d personally love a computer experience which emphasized ‘flow’ and gradual, constant change. No longer would every little change pull your attention away from an important task. Instead, those Mail notifications, system messages and the like could gently change without you noticing, until you decided you wanted to actually look.</description>
	</item>
	<item>
		<title>Impairment and Design</title>
		<link>http://tc.eserver.org/33373.html</link>
		<guid>http://tc.eserver.org/33373.html</guid>
		<description>We are all impaired to some amount. I realized this a few years ago as a musician, moving heavy amplifiers to gigs. Those little ramps that had been required by law (at least here in Australia) for wheelchairs were my saving grace.. instead of lifting the hefty equipment I could roll it into the building. It probably saved me more than once from back injury. And yet, there would be no way the institutions would have put in those ramps for my convenience.</description>
	</item>
	<item>
		<title>Touchscreen: Usability Guidelines</title>
		<link>http://tc.eserver.org/33293.html</link>
		<guid>http://tc.eserver.org/33293.html</guid>
		<description>Are touchscreens always good news for users? Our consultants suggest guidelines to ensure touchscreen devices are both usable and useful.</description>
	</item>
	<item>
		<title>Guidelines on the Common Features of Mobile Phone Interfaces</title>
		<link>http://tc.eserver.org/33294.html</link>
		<guid>http://tc.eserver.org/33294.html</guid>
		<description>An ever increasing range of mobile phones are appearing on the market, each with their own features, designs and interfaces. Our extensive experience of working with a wide range of phones suggests that, despite their many differences, there are some user interface requirements common to all mobile phones. These requirements are presented as guidelines below.</description>
	</item>
	<item>
		<title>Image Links vs. Text Links</title>
		<link>http://tc.eserver.org/33203.html</link>
		<guid>http://tc.eserver.org/33203.html</guid>
		<description>Years back, we compared successful clickstreams (clickstreams that resulted in users accomplishing their goals, as observed in tons of usability tests) with unsuccessful clickstreams (clickstreams where users abandoned their goals before completing), looking for any clues that would help us predict behaviors in one that we didn’t see in the other.&#xD;&#xD;One factor we looked for was whether the clickstreams contained image links versus text links — does one type of link show up more often in successful clickstreams than the other.&#xD;&#xD;Our finding was when users clicked in image links they were just as likely to succeed or fail as when the clicked on text links. There was no statistically-meaningful difference.</description>
	</item>
	<item>
		<title>Interface Design and Optimization of Reading of Continuous Text</title>
		<link>http://tc.eserver.org/33179.html</link>
		<guid>http://tc.eserver.org/33179.html</guid>
		<description>At present, we do not know how to optimize reading via electronic equipment. In this chapter, some considerations that may help us do this in the future will be raised, and some of the relevant evidence and theory that do exist will be cited and briefly highlighted. The focus of this paper is on reading of continuous text, whether in linear form or hypertext form, and with or without the presence of graphics or other types of information.&#xD;</description>
	</item>
	<item>
		<title>Typography and the User Interface</title>
		<link>http://tc.eserver.org/33120.html</link>
		<guid>http://tc.eserver.org/33120.html</guid>
		<description>While processing speed and computational flexibility have grown at incredible rates, our displays, the most human-facing elements of our digital lives, lag behind.</description>
	</item>
	<item>
		<title>Where Visual Literacy and Interface Design Meet</title>
		<link>http://tc.eserver.org/32983.html</link>
		<guid>http://tc.eserver.org/32983.html</guid>
		<description>Scientists tell us that visual communication is natural human behaviour which all normally sighted persons engage in every day and take for granted, yet it is the product of a complex human intelligence that is very poorly understood.</description>
	</item>
	<item>
		<title>Clean, Cutting-Edge UI Design Cuts McAfee&apos;s Support Calls by 90%</title>
		<link>http://tc.eserver.org/33001.html</link>
		<guid>http://tc.eserver.org/33001.html</guid>
		<description>When McAfee Inc. recently introduced its ProtectionPilot software--a dashboard-type management console for its Active VirusScan SMB Edition and Active Virus Defense SMB Edition suites--the trial downloads were fast and furious: In the first 10 weeks after release, more than 20,000 users went online to get a copy.</description>
	</item>
	<item>
		<title>Interior Design Versus Product Design</title>
		<link>http://tc.eserver.org/33011.html</link>
		<guid>http://tc.eserver.org/33011.html</guid>
		<description>From my outsider’s point of view, automobile interior design seems to be first and foremost about appearance, about style. Function matters, but it is not the primary focus, except for anomalies, such as when consumers force cupholders down the throats of reluctant designers or insist upon easy to fold rear seats for SUVs and the ilk. It feels as if dashboard designers see functions as irritants: so many controls and devices, so little room. How can we ever manage?</description>
	</item>
	<item>
		<title>The Effect of Input Device on Video Game Performance</title>
		<link>http://tc.eserver.org/32802.html</link>
		<guid>http://tc.eserver.org/32802.html</guid>
		<description>First-person shooter (FPS) games have become increasingly popular, and the player’s ability to accurately control their weapon is very important in these games. This study assesses players’ accuracy on eliminating targets in the FPS game Star Wars Battlefront II using three different input devices (mouse, Playstation 2 controller, and joystick) with two different rifle types (sniper and blaster rifle). No significant performance differences were found between input devices although subjectively participants believed they peformed the worst with the joystick.</description>
	</item>
	<item>
		<title>Fun with Overflows</title>
		<link>http://tc.eserver.org/32672.html</link>
		<guid>http://tc.eserver.org/32672.html</guid>
		<description>Making use of the overflow and scrollLeft DOM property to scroll elements is a much more effective use of the CPU, over animating using CSS top/left. So this episode of J4D demonstrates the same effect used in two completely different ways.</description>
	</item>
	<item>
		<title>Toward a More Human Interface Device: Integrating the Virtual and Physical</title>
		<link>http://tc.eserver.org/32676.html</link>
		<guid>http://tc.eserver.org/32676.html</guid>
		<description>As UX professionals, we often take for granted the fact that our users will be dealing with a keyboard, mouse or track pad, and monitor. We think about users’ physical relationship with their digital devices very selectively, if at all. But, as we explore new human interface devices and incorporate new interactions into our designs, we have the opportunity to create deep connections between users and their technology.</description>
	</item>
	<item>
		<title>Transforming Taiwan Aboriginal Cultural Features into Modern Product Design: A Case Study of a Cross-Cultural Product Design Model</title>
		<link>http://tc.eserver.org/32585.html</link>
		<guid>http://tc.eserver.org/32585.html</guid>
		<description>With their beautiful and primitive visual arts and crafts, Taiwan’s aboriginal cultures offer great potential for enhancing design value and becoming recognized in the global market. Evidence shows very high prospects for Taiwan’s local cultures to become crucial cultural elements in future design applications. The purpose of this paper is to explore the meaning of cultural objects from Taiwan’s aboriginal cultures and to extract their cultural features. The paper attempts to illustrate how, by enhancing the original meaning and images of these cultural features and by taking advantage of new production technologies, they can be transformed into modern products that meet the needs of the contemporary consumer market.</description>
	</item>
	<item>
		<title>Emotion and Voice User Interfaces</title>
		<link>http://tc.eserver.org/32589.html</link>
		<guid>http://tc.eserver.org/32589.html</guid>
		<description>When you hear the term voice user interface (VUI), what comes to mind? Most likely, memories of an interactive voice response system (IVR) for customer service arise. IVRs are certainly not going away. For many companies, they remain the foremost contact point with customers. But voice user interfaces are more than just IVRs. In fact, VUIs have tremendous potential for enhancing the experience of any mobile phone user. As the use of mobile devices and applications proliferates internationally, understanding how to integrate, or mash up, graphic user interfaces (GUI) and VUIs is becoming critically important.</description>
	</item>
	<item>
		<title>Zebra Striping: More Data for the Case</title>
		<link>http://tc.eserver.org/32238.html</link>
		<guid>http://tc.eserver.org/32238.html</guid>
		<description>I recently conducted a study into the helpfulness (or lack thereof) of zebra striping—the shading of alternate rows in a table or form. The study measured performance as users completed a series of tasks and found no statistically significant improvement in accuracy—and very little statistically significant improvement in speed when zebra stripes were implemented.</description>
	</item>
	<item>
		<title>What We Can Learn from Microsoft Mojave</title>
		<link>http://tc.eserver.org/32073.html</link>
		<guid>http://tc.eserver.org/32073.html</guid>
		<description>A pretty interface doesn’t make an application or website. Even the early releases of Microsoft Vista looked amazing.  The graphics, interface, and &apos;look&apos; of the system were much more impressive than XP.  But looks alone don’t make the package.  It lacked in usability, creating error messages and not having a standard navigation schema.  Users didn’t know if they were to click a button, an image, or text to complete their task.  It is important to create a standardized and intuitive interface, as well as nice looking, so that users can navigate your site or application.</description>
	</item>
	<item>
		<title>Creating a Digital World: Data As Design Material</title>
		<link>http://tc.eserver.org/32029.html</link>
		<guid>http://tc.eserver.org/32029.html</guid>
		<description>The common wisdom is that we now live in the age of information; the freedom and access we have to data is unprecedented in history; and the efficiency and convenience of online commerce, research, and communication has already transformed our lives for the better. While this is true, of course, our excitement should be tempered by a few realizations.</description>
	</item>
	<item>
		<title>IDEA 2008: An Interview with Bill DeRouchey</title>
		<link>http://tc.eserver.org/31997.html</link>
		<guid>http://tc.eserver.org/31997.html</guid>
		<description>Bill DeRouchey is fascinated with buttons and the history of interface design. He talks to us as he prepares for IDEA 2008, October 7-8. In Chicago, Bill hopes to help attendees expand their sources of inspiration to&#xD;include just about anything in their everyday lives.</description>
	</item>
	<item>
		<title>People Finder: Searching Without Logic? Improving the People Finder Application</title>
		<link>http://tc.eserver.org/31996.html</link>
		<guid>http://tc.eserver.org/31996.html</guid>
		<description>One of the most frequent tasks on many intranets is finding people within the company. Providing an effective way to search people is thus a key goal in designing intranets. This goal becomes even more important for an organization like Emirates, a leading international airline, which has over 35,000 employees with over 140 nationalities and where more people are likely to use this feature more frequently.</description>
	</item>
	<item>
		<title>Your New Excuse to Get an Xbox: How UX Professionals Can Learn from Video Game Design</title>
		<link>http://tc.eserver.org/31999.html</link>
		<guid>http://tc.eserver.org/31999.html</guid>
		<description>Games are fun, addictive, beautiful, and immersive. Websites, for the most part, are not. Take a moment and think about what video games look like, what they sound like, the way you can move on the screen, what “you” can be. Think of how you feel when you play and who you play with. Consider the launch of Halo 3 on Xbox 360, with unprecedented graphics, sound, and interactivity that Time.com called “refined to the point where it delivers only pure unadulterated gaming bliss.”</description>
	</item>
	<item>
		<title>OK-Cancel or Cancel-OK?</title>
		<link>http://tc.eserver.org/31907.html</link>
		<guid>http://tc.eserver.org/31907.html</guid>
		<description>Should the OK button come before or after the Cancel button? Following platform conventions is more important than suboptimizing an individual dialog box. </description>
	</item>
	<item>
		<title>Top-10 Application-Design Mistakes</title>
		<link>http://tc.eserver.org/31916.html</link>
		<guid>http://tc.eserver.org/31916.html</guid>
		<description>Application usability is enhanced when users know how to operate the UI and it guides them through the workflow. Violating common guidelines prevents both. </description>
	</item>
	<item>
		<title>Barrierefreie Informationstechnik: ein Thema nicht nur für behinderte Menschen</title>
		<link>http://tc.eserver.org/31147.html</link>
		<guid>http://tc.eserver.org/31147.html</guid>
		<description>Abgeflachte Bürgersteige, Rampen statt Stufen, tiefergelegte Busse - an den alltäglichen baulichen Barrieren für Kinderwägen und Rollstuhlfahrer wird gearbeitet. Im IT-Bereich dagegen ließ Barrierefreiheit bislang auf sich warten: Viele Websites sind nicht für jeden zugänglich. Mit dem Gesetz zur Gleichstellung behinderter Menschen sind öffentliche Institutionen seit Anfang Mai 2002 verpflichtet, ihre Websites barrierefrei zu gestalten.</description>
	</item>
	<item>
		<title>Usability and Taking Chances  </title>
		<link>http://tc.eserver.org/31113.html</link>
		<guid>http://tc.eserver.org/31113.html</guid>
		<description>A blog post that discusses the XO laptop, and the risks that the designers and developers took when creating the user interface for the device - for the most part they succeeded in creating an intuitive interface and a usable computer.</description>
	</item>
	<item>
		<title>Looking At GUI Libraries: Spotlight On Infragistics</title>
		<link>http://tc.eserver.org/31036.html</link>
		<guid>http://tc.eserver.org/31036.html</guid>
		<description>As a Graphical User Interface (GUI) programmer, I have many interface development tools to choose from. Over the years, my development environment changes to accommodate my needs. This often includes learning new languages and the tools that go with them.</description>
	</item>
	<item>
		<title>Better Business Analysis through User Interface Prototyping</title>
		<link>http://tc.eserver.org/30875.html</link>
		<guid>http://tc.eserver.org/30875.html</guid>
		<description>User Interface (UI) prototyping can help business analysts to address many challenges, even though it is usually considered to be part of design rather than requirements analysis. The rest of this article briefly describes UI prototyping, and some of the benefits and risks it offers to business analysts.</description>
	</item>
	<item>
		<title>Web 2.0 Can Be Dangerous</title>
		<link>http://tc.eserver.org/30828.html</link>
		<guid>http://tc.eserver.org/30828.html</guid>
		<description>AJAX, rich Internet UIs, mashups, communities, and user-generated content often add more complexity than they&apos;re worth. They also divert design resources and prove (once again) that what&apos;s hyped is rarely what&apos;s most profitable.</description>
	</item>
	<item>
		<title>The Perpetual Super-Novice</title>
		<link>http://tc.eserver.org/30824.html</link>
		<guid>http://tc.eserver.org/30824.html</guid>
		<description>The problem of the perpetual super-novice is the tendency of people to stop learning about a digital product--whether it&apos;s an operating system, desktop application, Web site, or hardware device.</description>
	</item>
	<item>
		<title>Build a Customizable RSS Feed Aggregator in PHP</title>
		<link>http://tc.eserver.org/30804.html</link>
		<guid>http://tc.eserver.org/30804.html</guid>
		<description>RSS (Rich Site Summary, RDF Site Summary, or Really Simple Syndication) has been around since the mid-1990s. Over the years, several variants of the RSS format have popped up and several claims have been made about its ownership. Despite these differences, RSS never ceased to serve its usefulness in distributing Web content from one Web site to many others. The popularity of RSS gave way to the growth of a new class of Web software called the feed reader, also known as the feed aggregator. Although there are several commercially available feed aggregators, it&apos;s easy to develop your own feed aggregator, which you can integrate with your Web applications. You&apos;ll appreciate this article&apos;s fully functional PHP code snippets, demonstrating the use of PHP-based server-side functions to develop a customizable RSS feed aggregator. In addition, you&apos;ll reap instant benefits from using the fully functional RSS feed aggregator code, which you can download from this article.</description>
	</item>
	<item>
		<title>Solid Ajax Applications, Part 2: Building Ajax Back Ends</title>
		<link>http://tc.eserver.org/30805.html</link>
		<guid>http://tc.eserver.org/30805.html</guid>
		<description>Back end processing -- server-side scripts and programs -- can&apos;t always be tossed into an Ajax application and behave well. Instead, careful planning to ensure data is sent in an appropriate and efficient form ensures your entire application is cohesive, rather than needlessly complex. Brett McLaughlin explains how a good server-side script complements Ajax behavior.</description>
	</item>
	<item>
		<title>Visio: The Interaction Designer&apos;s Nail Gun</title>
		<link>http://tc.eserver.org/30803.html</link>
		<guid>http://tc.eserver.org/30803.html</guid>
		<description>How to use Visio for rapid prototyping - now with scrolling pages and sketchy interface widgets.</description>
	</item>
	<item>
		<title>Creating Coloured Hyperlinks in an Index in a PDF File</title>
		<link>http://tc.eserver.org/30786.html</link>
		<guid>http://tc.eserver.org/30786.html</guid>
		<description>This article explains how to create coloured hyperlinks in an index in a PDF file, using Microsoft Word as the source document for the PDF file.&#xD;&#xD;Many authors create PDF files using Word as the source document. Most Word-to-PDF converters create a hyperlink in the PDF file if a hyperlink exists in the Word document. Unfortunately, Word does not create hyperlinked cross-references in an index, so no PDF creation tool can directly generate a hyperlinked index.&#xD;&#xD;The Sonar Bookends Activate plug-in for Acrobat creates hyperlinks for page numbers in indexes in PDF files. The plug-in does not change the colour of new hyperlinks, and it does not create visible rectangles for the hyperlinks. This article explains how to colour the hyperlinks in the Word source document using macro.</description>
	</item>
	<item>
		<title>Building the Front End: Craft Intelligent and Intuitive Front Ends for Ajax Applications</title>
		<link>http://tc.eserver.org/30665.html</link>
		<guid>http://tc.eserver.org/30665.html</guid>
		<description>With Ajax still one of the industry&apos;s hottest buzzwords, more and more applications are being built with Ajax technologies. However, it&apos;s not always easy to build a good application. This article focuses on how to build intuitive, easy-to-use Ajax-driven applications.</description>
	</item>
	<item>
		<title>GUI Bloopers 2.0: Common User Interface Design DON&apos;Ts and DO&apos;s</title>
		<link>http://tc.eserver.org/30642.html</link>
		<guid>http://tc.eserver.org/30642.html</guid>
		<description>GUI Bloopers 2.0 describes common user-interface mistakes found in today&apos;s software products and services, and provides design rules and guidelines to avoid them. Johnson describes the design decisions that lead to misuse of controls, poor navigation, prose-riddled labels, bad design and layout, faulty interaction, and poor responsiveness. GUI Bloopers 2.0 is well illustrated with hundreds of examples from real products and online services, and stories from his own experience.</description>
	</item>
	<item>
		<title>Foundations of Interaction Design</title>
		<link>http://tc.eserver.org/30632.html</link>
		<guid>http://tc.eserver.org/30632.html</guid>
		<description>An interview with David Malouf on his article, Foundations of Interaction Design. We discuss several foundations of Interaction design including time, metaphor, abstraction, and negative space. David also provides greater detail to comments posted on his article from readers from around the world.</description>
	</item>
	<item>
		<title>Uses for Virtual Reality in the Workplace and Classroom</title>
		<link>http://tc.eserver.org/30609.html</link>
		<guid>http://tc.eserver.org/30609.html</guid>
		<description>Virtual reality and game technology can be used in the technical communication classrooms and the workplace as well as the laboratory. Because our communication into the 21st century will take many &quot;technical&quot; forms, the technology, creativity, degree of interaction, and multimedia designs of virtual reality simulations should become part of our communication technology in the 1990s. Although hypertext, hypermedia, computer-aided design (CAD), and multimedia, multisensory training applications are becoming more common in the workplace, the concept of virtual reality has seldom been translated into practical applications that require business and technical communicators to have special skills. As well, advances in holographic information create exciting new educational designs for the future.</description>
	</item>
	<item>
		<title>Task Analysis and Associated User Interfaces for CD-ROM</title>
		<link>http://tc.eserver.org/30586.html</link>
		<guid>http://tc.eserver.org/30586.html</guid>
		<description>With its enormous storage capacity, cost-effectiveness, and convenience, the CD-ROM is quickly becoming a significant research and business tool. To retrieve data from the CD-ROM, users access a search program that helps them select a subset of data from the entire database. Because the selection includes a series of complex tasks that most users are unfamiliar with, user interfaces must be task-oriented as well as intuitive and interactive. Even with a variety of interfaces, users wanted more paper documentation. When users have little experience or familiarity with the concepts and the tasks, written documentation is a better information source than computer-based information.</description>
	</item>
	<item>
		<title>Easy, Intuitive and Metaphor, and Other Meaningless Words</title>
		<link>http://tc.eserver.org/30479.html</link>
		<guid>http://tc.eserver.org/30479.html</guid>
		<description>A vital skill for designers is to notice fine detail in the other designs which form part of the technological ecosystem in which their design will live. For example, on Mac OS there are now two different styles of text entry fields for forms. One has square corners, and is used for general data entry. The other has rounded ends, and is used for entering searches. I was recently outraged to find a piece of software which used the rounded style for data entry. This kind of design vandalism muddies the rules which users would otherwise learn, and devalues all software on the platform.</description>
	</item>
	<item>
		<title>Writing at the User Interstices</title>
		<link>http://tc.eserver.org/30354.html</link>
		<guid>http://tc.eserver.org/30354.html</guid>
		<description>The most coveted writing assignment in the computer industry is the overview of an integrated software package. It calls for careful pacing, creative metaphor, and lavish graphics, all integrated with the highest skill. Here stands the pinnacle of a career, to be &apos;writing at the user interface.&apos;</description>
	</item>
	<item>
		<title>The Gap Between 25 Seconds and 5 Seconds</title>
		<link>http://tc.eserver.org/30225.html</link>
		<guid>http://tc.eserver.org/30225.html</guid>
		<description>If designers took the perspective of users in the design of air conditioners, perhaps the wait for the cold air would not have been 25 seconds, unless you really think that 25 seconds of waiting time is fun for users.</description>
	</item>
	<item>
		<title>Generic Commands</title>
		<link>http://tc.eserver.org/30196.html</link>
		<guid>http://tc.eserver.org/30196.html</guid>
		<description>Applications can give users access to a richer feature set by using the same few commands to achieve many related functions.</description>
	</item>
	<item>
		<title>Developing Interface Standards: Compliance From a Corporate Perspective</title>
		<link>http://tc.eserver.org/30146.html</link>
		<guid>http://tc.eserver.org/30146.html</guid>
		<description>This paper discusses the role of an information developer in defining application interface standards and ensuring compliance across all applications. An interface, such as an application screen or system-generated report, should be consistent to enhance ease-of-processing for the end users.</description>
	</item>
	<item>
		<title>The Composite Intelligence of Virtual Assistants</title>
		<link>http://tc.eserver.org/30025.html</link>
		<guid>http://tc.eserver.org/30025.html</guid>
		<description>Five levels of software intelligence can, in my opinion, make the dream of virtual assistants a reality. Collectively, they make up the concept of composite intelligence, which comprises various software components--each gifted with some moderate degree of intelligence.</description>
	</item>
	<item>
		<title>Canonical Abstract Prototypes for Abstract Visual and Interaction Design</title>
		<link>http://tc.eserver.org/30012.html</link>
		<guid>http://tc.eserver.org/30012.html</guid>
		<description>Abstract user interface prototypes offer designers a form of representation for specification and exploration of visual and interaction design ideas that is intermediate between abstract task models and realistic or representational prototypes. Canonical Abstract Prototypes are an extension to usage-centered design that provides a formal vocabulary for expressing visual and interaction designs without concern for details of appearance and behavior. A standardized abstract design vocabulary facilitates comparison of designs, eases recognition and simplifies description of common design patterns, and lays the foundations for better software tools. This paper covers recent refinements in the modeling notation and the set of Canonical Abstract Components. New applications of abstract prototypes to design patterns are discussed, and variations in software tools support are outlined.</description>
	</item>
	<item>
		<title>Essential Use Cases and Responsibility in Object-Oriented Development</title>
		<link>http://tc.eserver.org/30021.html</link>
		<guid>http://tc.eserver.org/30021.html</guid>
		<description>Essential use cases are abstract, lightweight, technology-free dialogues of user intentions and system responsibilities that effectively capture requirements for user interface design. Employing essential use cases in typical object-oriented development processes requires designers to translate them into conventional use cases, costing time, imposing rework, and delaying work on the object-oriented development until the user interface design is complete. We describe how essential use cases can drive object-oriented development directly, without any intervening translation, allowing user interface development to proceed in parallel. Working with essential use cases yields some unexpected further benefits: analysts can take advantage of recurring patterns in essential use cases, and the crucial common vocabulary of responsibilities lets designers trace directly from the essential use cases to the objects in their design.</description>
	</item>
	<item>
		<title>From Essential Use Cases to Objects</title>
		<link>http://tc.eserver.org/30014.html</link>
		<guid>http://tc.eserver.org/30014.html</guid>
		<description>One of the main motivations for essential use cases was the context of user interface design. We, however, have been exploring the application of essential use cases in general object-oriented system development. Our experience has been very positive, and we found advantages to essential use cases that assist in both analysis and in design. This paper outlines two techniques involving essential use cases: use of role-play in requirements analysis, and distribution of system requirements from essential use cases to objects.</description>
	</item>
	<item>
		<title>Instructive Interaction: Making Innovative Interfaces Self-Teaching</title>
		<link>http://tc.eserver.org/30020.html</link>
		<guid>http://tc.eserver.org/30020.html</guid>
		<description>An innovative approach to enhancing ease of use and learning for novel user interfaces is described. Instructive interaction comprises a body of techniques based on a learning-by-doing model that is supported by three design principles: explorability, predictability, and guidance. Taken together, these principles form the basis for creative designs that can support highly efficient production use by experienced users while also enabling new users to understand and make effective use of an unfamiliar system almost immediately. The underlying principles of instructive interaction are presented here and an assortment of specific techniques based on these principles is described.</description>
	</item>
	<item>
		<title>Develop an Ajax-Based File Upload Portlet Using DWR</title>
		<link>http://tc.eserver.org/29964.html</link>
		<guid>http://tc.eserver.org/29964.html</guid>
		<description>File upload is a basic function of today&apos;s Web portals. In this article, authors Xiaobo Yang and Rob Allan describe how to develop an Ajax-based file upload JSR 168-compliant portlet using DWR (Direct Web Remoting). DWR is an ideal Ajax framework for Java developers that dynamically generates JavaScript based on server-side deployed Java classes. You will learn how you can use DWR to retrieve file upload progress from the portal server.</description>
	</item>
	<item>
		<title>Framework of Product Experience</title>
		<link>http://tc.eserver.org/29822.html</link>
		<guid>http://tc.eserver.org/29822.html</guid>
		<description>In this paper, we introduce a general framework for product experience that applies to all affective responses that can be experienced in human-product interaction. Three distinct components or levels of product experiences are discussed: aesthetic experience, experience of meaning, and emotional experience. All three components are distinguished in having their own lawful underlying process.</description>
	</item>
	<item>
		<title>A Usability Evaluation of Web Map Zoom and Pan Functions</title>
		<link>http://tc.eserver.org/29819.html</link>
		<guid>http://tc.eserver.org/29819.html</guid>
		<description>Due to limitations on screen size and resolution, the usability of web maps relies heavily on their interface design. The main goal of this research is to find better interface designs for web maps and to facilitate their usage by the public. The research consists of two stages of investigation: (a) a survey on the operation interfaces of popular web maps; and (b) a usability evaluation of simulated interfaces by measuring task performance and conducting subjective evaluations.</description>
	</item>
	<item>
		<title>Is Consistency Boring?</title>
		<link>http://tc.eserver.org/29793.html</link>
		<guid>http://tc.eserver.org/29793.html</guid>
		<description>What do customers want from our software and documentation? They want to accomplish tasks, and to obtain information about tasks, as quickly and painlessly as possible. Do they also expect to be entertained along the way? No, not when there is work to be done. Years of usability analysis in the software industry indicates very clearly that clarity and ease-of-use is topmost on the minds of software users.</description>
	</item>
	<item>
		<title>How Design Documents Enhance Information Product Development Process Quality</title>
		<link>http://tc.eserver.org/29780.html</link>
		<guid>http://tc.eserver.org/29780.html</guid>
		<description>Panelists from LSI Logic Storage Systems review their company&apos;s approach to enhancing process quality by using design documents as process enforcement and project-planning tools for planning the development of information products (IP). Hear how effective planning solves problems that occur during the IP development process and how capturing the planning elements in design documents helps solve role-based problems for developers, editors, and managers. Discuss the many problems design documents help project teams solve: they help developers solidify the IP development task sequence, they help editors define the rhetorical context, and they help managers reduce the cost of rework.</description>
	</item>
	<item>
		<title>Metaphor-Based Design of High-Throughput Screening Process Interfaces</title>
		<link>http://tc.eserver.org/29454.html</link>
		<guid>http://tc.eserver.org/29454.html</guid>
		<description>This paper describes work on developing usable interfaces for creating and editing methods for high-throughput screening of chemical and biological compounds in the domain of life sciences automation. A modified approach to metaphor-based interface design was used as a framework for developing a screening method editor prototype analogous to the presentation of a recipe in a cookbook. The prototype was compared to an existing screening method editor application in terms of effectiveness, efficiency, and satisfaction of novice users and was found to be superior.</description>
	</item>
	<item>
		<title>Keeping Tabs</title>
		<link>http://tc.eserver.org/29288.html</link>
		<guid>http://tc.eserver.org/29288.html</guid>
		<description>The original tab signaled an information storage revolution and helped enable everything from management consulting to electronic data processing.</description>
	</item>
	<item>
		<title>Your Design Is Infringing On My Patent: The Case Against User Interface and Interaction Model Patents and Intellectual Property</title>
		<link>http://tc.eserver.org/29290.html</link>
		<guid>http://tc.eserver.org/29290.html</guid>
		<description>Companies often file for and the US government actually grants patents for user interface and interaction design &apos;innovations&apos; that are either strikingly obvious or have appeared before in other systems.</description>
	</item>
	<item>
		<title>Testing the Usability of Interactive Visualizations for Complex Problem-Solving: Findings Related to Improving Interfaces and Help</title>
		<link>http://tc.eserver.org/29051.html</link>
		<guid>http://tc.eserver.org/29051.html</guid>
		<description>In visual querying, users analyze data for their decisions and problems by interacting with graphics that are dynamic and linked. This querying paradigm is new, a dramatic break from the more familiar retrieving of data via search statements and displaying of it in static charts and graphs. For this new visual querying paradigm, analysts conceptually and operationally need to master new approaches. To discover salient relationships, they need to manipulate displays. To drill down for detail or causes, they have to select data of interest directly from a graph. And to draw inferences, they have to consider meanings across several dynamically linked graphics. With the aim of studying users success in these new approaches, particularly focusing on the approach of directly selecting data from graphs, I conducted a scenario-based usability test with 10 data analysts. They interacted with visualizations to complete a realistic complex analysis evaluating employee performance. Test findings reveal a range of difficulties in visual selection that, at times, gave rise to inaccurate selections, invalid conclusions, and misguided decisions. To overcome these difficulties, support for visual selection needs to be built into interfaces and help. Results and recommended improvements are presented.</description>
	</item>
	<item>
		<title>Simplicity: The Distribution of Complexity</title>
		<link>http://tc.eserver.org/28936.html</link>
		<guid>http://tc.eserver.org/28936.html</guid>
		<description>Achieving simplicity is not that simple when you are dealing with complex modern device design. Rob Tannen mused on lazy shortcuts, artificial constraints and Maeda&apos;s crusade on the complex.</description>
	</item>
	<item>
		<title>Designing Interfaces</title>
		<link>http://tc.eserver.org/28678.html</link>
		<guid>http://tc.eserver.org/28678.html</guid>
		<description>Over the past few years, I have come to appreciate the power patterns have as a shorthand that lets software engineers communicate their design intentions. Being able to discuss an Observer or Factory pattern with other engineers quickly moves the design discussion to more substantive concerns.</description>
	</item>
	<item>
		<title>From GUI to E(motional) UI</title>
		<link>http://tc.eserver.org/28683.html</link>
		<guid>http://tc.eserver.org/28683.html</guid>
		<description>How ironic that we think we can get more exact results from our computers by emulating human interaction, but when we want exact results from human interaction, we unintentionally emulate computers. Engineering, air traffic control, legal contracts--in all endeavors where precise communication is critical--our success has depended on washing out human emotion and natural language in favor of formal procedures and protocols, complete with a detailed domain-specific language.</description>
	</item>
	<item>
		<title>New Life for Product Documentation</title>
		<link>http://tc.eserver.org/28686.html</link>
		<guid>http://tc.eserver.org/28686.html</guid>
		<description>Here are some &apos;truths&apos; we&apos;ve all heard: &apos;Documentation is just a band-aid for poor design.&apos; &apos;Real users don&apos;t read manuals.&apos; &apos;Super users never read anything.&apos; &apos;Help doesn&apos;t.&apos; But are they really true? I&apos;ve seen some signs of life in the use of documentation for digital products recently.</description>
	</item>
	<item>
		<title>The Atmosphere at Interaction Frontiers 2006</title>
		<link>http://tc.eserver.org/28675.html</link>
		<guid>http://tc.eserver.org/28675.html</guid>
		<description>Interaction Frontiers 2006 was a great experience, with some margin for improvement. I&apos;m sure next year&apos;s Interaction Frontiers will be even bigger and better.</description>
	</item>
	<item>
		<title>Effective User Assistance Design: Ten Best Practices</title>
		<link>http://tc.eserver.org/28661.html</link>
		<guid>http://tc.eserver.org/28661.html</guid>
		<description>In a utopian world, a product would be so perfect it would not need any user assistance at all. But in reality, products aren&apos;t perfect, and users need assistance through different stages of their use. User assistance (UA)--in the form of manuals or online Help--guides users in their tasks, suggests better ways of getting their work done, and provides directions for troubleshooting their problems.</description>
	</item>
	<item>
		<title>Instructional Text in the User Interface: Some Counterintuitive Implications of User Behaviors</title>
		<link>http://tc.eserver.org/28658.html</link>
		<guid>http://tc.eserver.org/28658.html</guid>
		<description>User assistance occurs within an action context--the user doing something with an application--and should appear in close proximity to the focus of that action--that is, the application it supports. The optimal placement of user assistance, space permitting, is in the user interface itself. We typically call that kind of user assistance instructional text. But when placing user assistance within an application as instructional text, we must modify conventional principles of good information design to accommodate certain forces within an interactive user interface. This column, User Assistance, talks about how the rules for effective instruction change when creating instructional text for display within the context of a user interface.</description>
	</item>
	<item>
		<title>Seeing the World in Symbols: Icons and the Evolving Language of Digital Wayfinding</title>
		<link>http://tc.eserver.org/28668.html</link>
		<guid>http://tc.eserver.org/28668.html</guid>
		<description>Of all the objects that occupy our digital spaces, there are none that capture the imagination so much as icons. As symbols, icons can communicate powerfully, be delightful, add to the aesthetic value of software, engage people&apos;s curiosity and playfulness, and encourage experimentation. These symbols are key components of a graphic user interface--mediators between our thoughts and actions, our intentions and accomplishments.</description>
	</item>
	<item>
		<title>Selection-Dependent Inputs</title>
		<link>http://tc.eserver.org/28659.html</link>
		<guid>http://tc.eserver.org/28659.html</guid>
		<description>Successful Web applications tend to grow--both in terms of capability and complexity. And this increasing complexity is often passed on to and absorbed by a Web application&apos;s forms. In addition to needing more input fields, labels, and Help text, forms with a growing number of options may also require selection-dependent inputs.</description>
	</item>
	<item>
		<title>The Dark Side of Prototyping</title>
		<link>http://tc.eserver.org/28499.html</link>
		<guid>http://tc.eserver.org/28499.html</guid>
		<description>Are there any downsides of prototyping? Not really. But as with everything else in life, you might stumble and hurt yourself if you don’t watch your step. This article points out some of the banana skins to steer clear of.</description>
	</item>
	<item>
		<title>Prototyping Beyond the Sunshine Scenario</title>
		<link>http://tc.eserver.org/28500.html</link>
		<guid>http://tc.eserver.org/28500.html</guid>
		<description>Prototypes often model one flow of interaction--the path that users are most likely to take. But when we create interaction designs with dynamic and complex flows, we often need to include deviations from the sunshine scenarios to see whether they work. In this article, we&apos;ll look at how to do this Visio and Axure.</description>
	</item>
	<item>
		<title>Productivity and Screen Size</title>
		<link>http://tc.eserver.org/28464.html</link>
		<guid>http://tc.eserver.org/28464.html</guid>
		<description>A study of the benefits of big monitors fails on two accounts: it didn&apos;t test realistic tasks, and it didn&apos;t test realistic use. Productivity is a key argument for workplace usability, but you must measure it carefully.</description>
	</item>
	<item>
		<title>The Impact of Globalization on User Interface Design</title>
		<link>http://tc.eserver.org/28414.html</link>
		<guid>http://tc.eserver.org/28414.html</guid>
		<description>Did you ever try to use a machine that has been programmed in a foreign language? Or perhaps, even with an unfamiliar character set? Suddenly everything seems to be different although only the language has changed. This is the situation faced by many foreign users that work with German machines.&#xD;&#xD;</description>
	</item>
	<item>
		<title>&amp;#30011;&amp;#38754;&amp;#12469;&amp;#12452;&amp;#12474;&amp;#12392;&amp;#29983;&amp;#29987;&amp;#24615;</title>
		<link>http://tc.eserver.org/28375.html</link>
		<guid>http://tc.eserver.org/28375.html</guid>
		<description>&amp;#22823;&amp;#12365;&amp;#12356;&amp;#30011;&amp;#38754;&amp;#12398;&amp;#21033;&amp;#28857;&amp;#12395;&amp;#12388;&amp;#12356;&amp;#12390;&amp;#12398;&amp;#12486;&amp;#12473;&amp;#12488;&amp;#12395;&amp;#12399;&amp;#12289;2 &amp;#12388;&amp;#12398;&amp;#38291;&amp;#36949;&amp;#12356;&amp;#12364;&amp;#12354;&amp;#12387;&amp;#12383;&amp;#12290;&amp;#29694;&amp;#23455;&amp;#30340;&amp;#12394;&amp;#12479;&amp;#12473;&amp;#12463;&amp;#12391;&amp;#12486;&amp;#12473;&amp;#12488;&amp;#12375;&amp;#12390;&amp;#12356;&amp;#12394;&amp;#12363;&amp;#12387;&amp;#12383;&amp;#12371;&amp;#12392;&amp;#12392;&amp;#12289;&amp;#29694;&amp;#23455;&amp;#30340;&amp;#12394;&amp;#21033;&amp;#29992;&amp;#26041;&amp;#27861;&amp;#12391;&amp;#12486;&amp;#12473;&amp;#12488;&amp;#12375;&amp;#12390;&amp;#12356;&amp;#12394;&amp;#12363;&amp;#12387;&amp;#12383;&amp;#12371;&amp;#12392;&amp;#12384;&amp;#12290;&amp;#29983;&amp;#29987;&amp;#24615;&amp;#12399;&amp;#12289;&amp;#21172;&amp;#20685;&amp;#29872;&amp;#22659;&amp;#12398;&amp;#12518;&amp;#12540;&amp;#12470;&amp;#12499;&amp;#12522;&amp;#12486;&amp;#12451;&amp;#12434;&amp;#35486;&amp;#12427;&amp;#19978;&amp;#12391;&amp;#37325;&amp;#35201;&amp;#12394;&amp;#38917;&amp;#30446;&amp;#12395;&amp;#12394;&amp;#12427;&amp;#12364;&amp;#12289;&amp;#12381;&amp;#12428;&amp;#12434;&amp;#35336;&amp;#28204;&amp;#12377;&amp;#12427;&amp;#22580;&amp;#21512;&amp;#12399;&amp;#12289;&amp;#27880;&amp;#24847;&amp;#28145;&amp;#12367;&amp;#34892;&amp;#12431;&amp;#12394;&amp;#12369;&amp;#12428;&amp;#12400;&amp;#12356;&amp;#12369;&amp;#12394;&amp;#12356;&amp;#12290;</description>
	</item>
	<item>
		<title>Mode in User Interface Design</title>
		<link>http://tc.eserver.org/28366.html</link>
		<guid>http://tc.eserver.org/28366.html</guid>
		<description>Perhaps you had, once or twice, experienced the following: When you logon to a software system, you are required to input a user name and password. In most situations, the system remembers your last input and the system automatically pre-fills in the username edit box, and the cursor will be directly placed in the password edit box. You tried typing in your password several times, only to be complained by the system that the password is wrong.</description>
	</item>
	<item>
		<title>Co-Design, China, and the Commercialization of the Mobile User Interface</title>
		<link>http://tc.eserver.org/28317.html</link>
		<guid>http://tc.eserver.org/28317.html</guid>
		<description>The mobile user interface is becoming a key differentiator for mobile telephony devices and services. The increased focus on usable, emotive, and branded user interfaces is the result of three key drivers.</description>
	</item>
	<item>
		<title>Building Disappearing Computers</title>
		<link>http://tc.eserver.org/28233.html</link>
		<guid>http://tc.eserver.org/28233.html</guid>
		<description>A trio of systems illustrates the challenges of designing large displays for use in ubiquitous computing environments that are, indeed, unremarkable.</description>
	</item>
	<item>
		<title>Mediating Group Dynamics through Tabletop Interface Design</title>
		<link>http://tc.eserver.org/28232.html</link>
		<guid>http://tc.eserver.org/28232.html</guid>
		<description>Our tabletop research efforts at Stanford University have focused on how tabletop user interfaces (UIs) might respond to and even influence a user group&apos;s social dynamics.</description>
	</item>
	<item>
		<title>The Bull&apos;s-Eye: A Framework for Web Application User Interface Design Guidelines</title>
		<link>http://tc.eserver.org/28093.html</link>
		<guid>http://tc.eserver.org/28093.html</guid>
		<description>A multi-leveled framework for user interface design guidelines of Web applications is presented. User interface design guidelines tend to provide information that is either too general, so that it is difficult to apply to a specific case, or too specific, so that a wide range of products is not supported. The framework presented is unique in that it provides a bridge between the two extremes. It has been dubbed the &quot;Bull&apos;s-Eye&apos; due to its five layers, represented as concentric circles. The center of the Bull&apos;s-Eye is the Component layer, followed by Page Templates, Page Flows, Interface Models and Patterns, and Overarching Features and Principles. To support this approach,requirements were gathered from user interface designers,product managers, UI developers, and product developers. Also, usability testing of the guidelines occurred on several levels, from broad guideline tests to more specific product tests. The guidelines and lessons learned are intended to serve as examples for others seeking to design families of Web applications or Web sites.</description>
	</item>
	<item>
		<title>Empirical Evaluation of a Popular Cellular Phone&apos;s Menu System: Theory Meets Practice</title>
		<link>http://tc.eserver.org/28018.html</link>
		<guid>http://tc.eserver.org/28018.html</guid>
		<description>A usability assessment entailing a paper prototype was conducted to examine menu selection theories on a small screen device by determining the effectiveness, efficiency, and user satisfaction of a popular cellular phone&apos;s menu system. Outcomes of this study suggest that users prefer a less extensive menu structure on a small screen device. The investigation also covered factors of category classification and item labeling influencing user performance in menu selection. Research findings suggest that proper modifications in these areas could significantly enhance the system&apos;s usability and demonstrate the validity of paper-prototyping which is capable of detecting significant differences in usability measures among various model designs.</description>
	</item>
	<item>
		<title>Does a Good User Interface Obviate the Need for Documentation?</title>
		<link>http://tc.eserver.org/27574.html</link>
		<guid>http://tc.eserver.org/27574.html</guid>
		<description>This question was raised on a programmer&apos;s group recently and I was intrigued. The programmer&apos;s point was that with many web applications these days there is no print documentation distributed to end users, and even if it existed, many users won&apos;t read it although this makes me wonder who&apos;s buying all those how-to books I see in the bookstore. The programmer suggested that applications should be designed without documentation and wondered about the impact that would have on design.</description>
	</item>
	<item>
		<title>Handheld Devices and the Flow of Functionality</title>
		<link>http://tc.eserver.org/27576.html</link>
		<guid>http://tc.eserver.org/27576.html</guid>
		<description>Handheld devices and small appliances pose a unique challenge to the interface designer. The blur between user interface and functionality (interface vs. interaction) is even more pronounced in these environments. The interface of any small device is extremely important; yet, more than ever, the necessity to build in exactly (and only) what is required by the user is extremely important!</description>
	</item>
	<item>
		<title>Perpetual Design-Think</title>
		<link>http://tc.eserver.org/27573.html</link>
		<guid>http://tc.eserver.org/27573.html</guid>
		<description>Software is sometimes poorly designed to begin with and the interface should be scrapped and rebuilt from scratch. But more often than not, I see software that started with a decent design and has since had features added onto it with each release, squeezed into the existing design rather than being designed in. People aren&apos;t in a design mindset but an &apos;enhancement&apos; mindset somehow.</description>
	</item>
	<item>
		<title>Task Based Documentation and Good User Interface Go Hand in Hand</title>
		<link>http://tc.eserver.org/27580.html</link>
		<guid>http://tc.eserver.org/27580.html</guid>
		<description>As I write the &apos;how to&apos; documentation based upon the in-process design, the weaknesses of my original design become apparent and I go back and forth from writing text to designing the software until it all flows.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/User-Interface.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>