Hot answers tagged


MS Windows User Experience Interaction Guidelines suggests the following: “Use the second person (you, your) to tell users what to do.” So use second person for error messages, help, window or page labels, on-page documentation, and other places where the app is telling the user about the user’s content. “Use the first person (I, me, my) to let users tell ...


Don't use My or Your. In most cases it's obvious whose they are. The only case you might want to do it is to differentiate e.g. between the user's documents and everyone's documents. In that case I would follow the Microsoft guidelines cited by Michael and use "Your Documents" and "All Documents". One of the worst UI bloopers in Windows XP is the use of ...


In addition to the related posts that JonW, called attention to, I think the biggest question to answer is using 'My' vs. 'Your'. We've had a previous question on the subject ("'Your' vs 'My' in user interfaces"), which is a great resource, but my favorite resource on the matter is the Yahoo Design Pattern Library. Yahoo advises to use 'Your' as the ...


How about just Username ? Just see how many sites including Stack Exchange, Google, Facebook, Twitter, etc don't show any other kind of salutation. They just show the username, which is hyperlinked to suggest that further profile information can be viewed by navigating to this link.


My favourite method is the one employed by Stack Exchange, Google, Flickr, and many other large sites with a strong focus on UX: use their username / real name combination as a clickable link. This has the dual benefit of hinting to the user if they are logged in as someone else, ans is more personal than the [pronoun] Account approach. Combinations of ...


I believe the cause is that handwriting generally has a higher x-height than printed type. That makes all-caps handwriting look more like printed small-caps, which are generally not considered rude, and actually end up looking formal. It's also true that all-caps used on the web now carries the connotation of screaming by convention (as mentioned by Juan ...


This is probably a bit tangential to your question, but when it comes to registration / sign up forms, "My" tends to perform better than "Your" conversion-wise. Check out this article - some really interesting examples there.


All capital handwriting is easier to read because it takes more time to write and forces the author to slow down. This increases legibility by requiring the writer to compose each individual letter one at a time. The variations for capital letters are less compared to lower case or cursive characters. Architects and engineers developed their particular ...


Caps are more difficult to read. This is because all letters have the same height, requiring some additional scrutiny to recognize each word (we read word by word, not letter by letter). So you can use caps to EMPHASIZE a short heading, but if you use it all along the text your readers might quit reading early because of the additional effort, i.e., slower ...


For me this would entirely depend on the context. If your definition of "username" was a user's first and last name, then "welcome..." would be more polite than "logged in as..."; on the contrary, if your "username" was just something the user used to log in, "logged in as..." would make more sense than "welcome...", as otherwise you're welcoming the user's ...


If you check "standard" login screens, like one Mac OSX or Android you can see that they usually don't rely on any headline at all. That's why I'd go with a simple "Suggested users:" as headline for the user list. In case somebody finds it too big-brotherish, you could add a small explanation on a secondary screen ("Who suggested these users?", or something ...


It doesn't matter... much. What you choose will not "kill" the overall experience either way. My suggestion is to find & solve for the bigger experience issues you have. (Or if this is your biggest problem, congrats on a great product!) However, what will kill the experience is if you: Switch back and forth between "your" and "my" with no rhyme or ...


According to Dustin Curtis "My X" makes the interface an extension of yourself whereas "Your X" makes it more of a social creature. To quote him from his great Yours vs. Mine article: I've settled pretty firmly in the camp of thinking that interfaces should mimic social creatures, that they should have personalities, and that I should be communicating ...


I have not seen any hard studies suggesting that either is better than the other. I would simply choose one convention and stick to it, keeping the same voice throughout your interface. That's if you even need the 'my' or 'your' - it's usually repetitive and unnecessary.


Generally in plain text, bold text is use to EMPHASISE a word. When everything that you write is being emphasised, the closest equivalent to continual emphasis in speech is shouting. The exception to this is when it is being used for labels and signs.


Generally, it is more aesthetic to use "Proper case". But I believe there is way more variation of the form of small letters than caps for handwriting. This is why in case of handwriting, caps are less difficult to decipher, which degrades the meaning of proper case.


In my opinion it's definitely better to identify the user than to use either pronoun. So the answer would be "fredley's account". It's more personal, but more importantly it makes it clear what's going on if the user is intentionally or accidentally accessing someone else's account. In the accidental case, I'd immediately think "wait a minute, I'm not ...


As a developer I usually go with "my", that way it seems the app is an extension of themselves instead of something being presented to them by someone else


You think there is one person, but there's not. There's two. At the very least, it's you and the reader. Or, you and the customer. Our service is not your service -- it belongs to the customer as well. You want to get across that they are part of the business, too. After all, a business without customers isn't actually a business. In my mind, using the ...


I would always use a positive statement because it is easier to understand, especially in the context of a checkbox. Mentally replace the checkbox with simply YES or NO. Then your statements are: YES: Send email notifications NO: Send email notifications YES: Don't send email notifications NO: Don't send email notifications I think the first ...


Ok, nobody coined this in both discussions, so here is something interesting for you to consider about the power of the opt-out. There was a rather famous study on organ transplant donations consent rates in psychology. …you will notice that pairs of similar countries have very different levels of organ donations. For example, take the following pairs ...


I was inclined to say Welcome at first, but then I noticed you're using the username. I think if you're still wondering whether it should be Logged in or Welcome, then Logged in as would make sense. Welcome would work better if it was Welcome . Logged in as admin_91 Welcome John


I think Fontbook should suit your requirements. It covers nearly 37,000 typefaces and every typeface has details about era, foundry, usage, designer, library, release date, number of sub families, font weights, glyphs per font, and trademark. It's a really well organized app. More about the app here.


First of all, the fact that you 'kinda love it' is of little practical matter when deciding upon such questions. Unless you are building the editor for yourself or are trying to represent/promote yourself via it by demonstrating your personality, which, I assume you are not, the end user and his/hers preference of style of communication should be the main ...


Loggin in several times per day could be annoying task. You try to solve it proposing more convinient way which could lead to less user's effort. Following you way, I just propose several steps further. Make the loggin process not only easy (even easy frequent tasks are boring), but fun, at least, pleasant, which will bring better experience. Pleasant Use ...


Allow me to offer another perspective: If security is important (such as for a banking site), I would prefer the term "logged in" because it explicitly indicates an open session, whereas "Welcome" simply implies that the website recognizes you, perhaps based on the last time you used it.


I don't think it really matters. Both indicate for the user that s/he is logged in (actually it's username (and preferably an avatar, for better visual indication) that indicates that user is logged in. I usually choose Welcome, username, as "welcome" it's more welcome.


Caps aren't significantly easier to read than standardized, separated non-caps in handwriting, the 'printed letters' of 'block letters'.


This is an interesting question, and one that actually seems to receive a lot of attention in areas outside of UI design. To take a page from the marketing peeps behind this new wave of "We're a happy, caring part of your family" approach to consumer contact-heavy industries like banking and sales, it's really about how you'd like your user to perceive ...

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