Tag Info

Hot answers tagged

58

"I'm sorry Dave, I'm afraid I can't do that." That scene from 2001: A space odyssey is a good example for why this can be a dangerous practice. Beware of anthropomorphising a computer to the point where the user starts ascribing malice to it. Error messages need to be non-personal to avoid the user feeling like the computer is complaining at them, or ...


54

Personalisation Igor. Content personalisation can be appropriate at times, like in an email or after login. Amongst a few, it makes the system appear more 'human', and can facilitate some personal 'bond' with the user. But one can argue that by attaching a name to a notification you won't achieve that (I see proper personalisation as real user-dependent ...


37

There are two big problems, from an internationalization perspective: How sure are you that your Name data contains the name the user is called by? Getting your name data format correct is a classically difficult problem. As soon as you add name wildcards to your error messages, they will become much more difficult to translate to other languages. Without ...


25

I don't think this is about user intuition - it's much more about writing style and conventions. The norm in forms is that the heading serves a category label to the adjectives/nouns below. So Car Features should do the trick here. Another norm is to use imperative statements, but mostly for interactive controls (not labels), still you could also phrase ...


12

You could try using the same approach Eclipse uses (or any other Java program I guess). They're using checkbox to indicate that all elements of the group are selected and a --symbol if only some of them are selected. Nothing selected All selected Not all elements selected One plus is that it's easy for the user to (un-)select the whole group. ...


11

The most relevant research I could find on this topic is a little dated. Fundamentally, adding user names to error messages deals with humanizing an interface. In a study of using human faces as part of computer interface [1] (admittedly, a step well beyond just including user names), the researchers found that increasing the humanization of an interface ...


6

Although 2001 SO is one of my favourite movie, here are a few things to keep in mind: Users don't like to read, the shorter the better. Kudos if it smarts and eventually witty. As a user, I would find quite redundant (and annoying) to have to read my name every 2 minutes. I'm already engaged in this 1 to 1 interaction with the interface. In a conversation, ...


6

The table is not organized in proper way, so you are trying to overcome this issue with your options. The problems are: Established reading pattern (by rows) makes it hard to distinguish the number (83%) as subtotal. It is perceived as normal row rather than subtotal one. Placing missed items info within the table is a logic error. The format of this row ...


5

Disclaimer: without more info as to what this is regarding, it's hard to say for sure. The following is based on gut feel. "I have a car..." feels more appropriate when it's contrasted with other sections, like "I have a motorcycle..." or "I have a bus...", perhaps with a top heading of "What kind of vehicle do you own?" That makes it easy to find the ...


5

I think there is a place for this - but it's not about calling users by name. That reminds me of middle-school programming assignments, which have a habit of starting with asking a user to type their name so the program can echo it back in messages. The more useful application of message personalization is to echo what has actually been done in a ...


5

You can categorize this under "menu bloat" ;) Help is an expected menu entry and rather than adding another menu (or using the application's menu, as they should) a lot of apps have over-used this position. In their defense, it's a menu users turn to when they have questions. I assume IA's are simply trying to capture people browsing for app information. ...


5

I'm wondering if the success/fail values in your graph have the same properties as those generated by a continuous integration server: Successful builds are essentially boring Sequential failed builds usually have the same cause If so, you could bundle "runs" of the same status together in the chart, something like this: (The righthand five bubbles ...


5

I think you could use sparklines as a compact visualization tool. This view is not precise, but it allows to view errors distribution and total error count for each process. More precise information is displayed in process specific screen. Light grey bar is an observation time window (a week or two, etc.). Dark line is an error occured within observed ...


5

I don't see anything wrong with using a partial sentence ending in an ellipses as a user prompt if the answer you're asking the user to input is a natural ending to the sentence fragment in your label. As you currently have it, the prompt and answers don't make a proper sentence: I have a car... blue Toyota Compare that with: My car is a... blue ...


4

The UX Book vs. The UX Scroll Having a single page of 1000+ entries is overwhelming. Whether it's quarterly reports or employee names, having that volume of them is massive. A user being able to sort their data is essential to agile navigation of data. I'd argue that aside from having more "pages" of data, having the option to sort the data in various ways ...


4

What Information Architecture is and what an Information Architect does/did are different. Information Architecture is the creation of navigational and meta data structures that affect the end experience, as mentioned in the previous answer. In reality an IA deals not only with information but also functionality. In my past role as an Information ...


4

Definitely Option B. Since you are listing them in pairs (today and yesterday), the most distinguishing factor between the two is not the value itself, but rather what day the value represents. Why? Because it designates the beginning of a trend or a point in a trend if you were displaying more than just 2 days. When looking at the bars, one naturally ...


3

The problem is more deep than readability. I see some points of improvements. Problem The more important issue is uncompleted interaction which could break your business goal. The goal, as you mentioned, is to sell some product. So the interaction sequence should look like: Find product View product details Sell product Instead you have only steps ...


3

If not going with Majed's suggestion, I'd choose number 2. The reason is simple: With so much information, I need to quickly find what I'm looking for. With elements using the exact same vertical space (they are all aligned), I find this much easier to do in the second case. I can scan the labels really quickly, and from there I know it's just moving to the ...


3

I think the major issue is that there is so much information attacking the reader at once. You need to dull down the immediate amount of information to the necessities. When the user clicks on the row, then the full amount of information will be displayed on the right side. The current layout is making it really difficult for the users to find what they ...


3

Can blame the Information Architect if you want to ;) Here is Chrome's help menu. Search bar for searching help topics, reporting issue and a button which takes you to the help page. That being said, it is a general pattern to include update and installation information in the help menu (look at PS and Aptana menus). Google does background updates and ...


2

This depends on the personality of your brand (site that is). MailChimp, OKCupid, etc. have done these things in the past where the error messages create an experience in there own. Example: Instead of "ERROR: Page unable to load" you might see "One of the Monkeys got lose, we will be back online as soon as we get him in his cage". It's the personality of ...


2

I bet you saw it many times. Just take a look: source I think you are supposed to develop something like the following: source


2

Information architects' tasks are: Mandatory create information categorization/classification create site navigation Optional, migrated from content-editor role define content specification assess current content create new content and metadata Frequently in a team there is not separate information architect's position, so this role is taken by ...


2

This seems to be a very specific problem, but what advantages are there to putting "Yesterday" after "Today". You need to have a very very good reason to violate chronological ordering, doubly so if you're going to use chronology as a large part of your legend. I just don't see it, (A) looks like a very bad idea. It certainly seems misleading, in (A) until ...


2

Why not use ellipsis to ask the user? When you end the sentence with an ellipsis, it looks like part of the sentence is missing. Ellipsis is mostly used to show the user the sentence is cut of. Here is an example of a question were the ellipsis is correctly used: Best aesthetically solution to overflowing data in a table


2

Users should never have to remember information from one screen to another (ux-discovery). Users should also always have feedback that makes them aware of their current status (in this case the progress they have made through the wizard) (ux-feedback). I would say that providing a little summary panel / column at the left side of the wizard is good practice ...


1

I would say A is preferred because users read from left to right. Equally, age is often demonstrated as in the past and therefore on the left (think of history timelines and calendars) I tried to do a quick Google for you to see what, well, Google were doing but I was only able to pull off a Salesforce and MediaPost example. Both of which demonstrate that A ...


1

Try searching for "Accessibility API", "UI Automation" or looking at Microsoft UI Automation. These types of tools allow you to access and even invoke menus and other UI elements in another application. Screen readers, screen magnifiers and such use this technique to make computers more accessible for the visually impaired and those with other ...


1

With assumptions and without seeing the example: Graying out a control typically means its read-only, static or not editable. A missing element means, well, that it does not exist. If the icon is tightly coupled with the control (its a clickable element or the like in context) then it should appear as the control does. My other opinion is a screen with ...



Only top voted, non community-wiki answers of a minimum length are eligible