The reason I believe it is important to have an apologetic tone is to ensure you are communicating to the user that, though a mistake has been made and he is interacting with a machine or application in this case, you still respect his action and are humanizing the mistake.
To quote this article from UXMatters:
“You’re going to display your error message ...
While Mervin's answer is excellent, I would go beyond saying it is "acceptable" or "preferred". I would say you "must" use an apologetic tone for one very good reason: if the user is making a mistake, it is because the user does not understand the rules or logic of the system. That is not the fault of the user! It is responsibility of the system to ...
I'd try abandon.
Are you sure you want to abandon the changes you made today?
[ Abandon changes ] [ Keep changes ]
I don't know what the back-out option does (does it commit the changes, or just close the dialog without taking any action), but the other button could be Keep changes, Commit changes, or just cancel.
I also like the idea of putting a ...
I use the word device to mean anything you use to do work which extends to computers and (most of the time) mobile phones. English StackExchange suggests using mobile device for describing phones and laptops, so I don't see why adding in "immobile devices" would ruin the effectiveness of using the word device to include phones, laptops, and tower PCs.
This is a great question and it may take a few more attempts to get it right. As a rule, people don't read, so a short description is key. I'd try:
Preferred Full Name
Nicknames are fine, titles are discouraged
Hope this helps
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 ...
| Past year | Past month | Past week |
This is much less likely to be misunderstood than "last year", and is a common way of presenting menus for selecting a time range. For example, the filters for Google search and Reddit's top posts use this exact wording.
Taking a step back: Why was this feature made available (visible) to the user in the first place?
If it is a feature not available to a specific user (or user class), hide it.
If it is a premium feature that you'd like to upsell - do so.
History export is a great way to backup your data, but is available on premium accounts only. Get in touch with your ...
I was having a discussion with my housemate who is a data analyst by trade, and the conclusion that we came to is that there are two sensible options here, depending on the amount of work you personally want to do (we're assuming here that the collection of gender data is actually useful to you, rather than simply of interest in which case it is almost ...
The fewer words the better, and no words at all are better than negative words.
Don't say why you think there might be a problem, or even that you think there is likely to be a problem. Instead just make it easy for them to contact you in the event that they do happen to come across a problem.
I quite liked an experience I had recently at surfdome where it ...
Are the listed words really synonyms? I cannot provide any references now (possibly because many software developers/producers do not consistently follow the distinction, either), but my impression is that at least abort and cancel are slightly different:
Cancel sounds pretty much like a routine operation. You can cancel something before it has really ...
A good error message should:
Let you know what the problem is.
Make you feel like there is something that you can do about it.
Speak like a human, and be a consistent extension of the personality of the rest of the application.
For generic error messages, you can't do much about the first point, but you can do something about the other two.
Do something ...
Answer "No". "Successfully" can be removed:
Joel Spolsky covered this issue very well here:
The basic rule of thumb is that:
"In fact, users don't read anything.
This may sound a little harsh, but you'll see, when you do usability tests, that there are quite a few users who simply do ...
Is there room for
no weight change
This is then easy to understand, and is clear that it's not any gain either.
Like the answer, I think you'd more than likely say something like "my weight hasn't changed since last week"
On a similar note, a 2% loss doesn't mean much to most, so would it be better to say
6lbs weight loss (2%)
Does the user need to know the specifics of what's happening?
Resubscribe or Subscribe would seem to be more consistent for the user as their perspective would be more with regard to whether or not they are receiving the notifications and not so much the how.
If it's clear, say it in the least number of words possible. If there is no confusion, then there is no problem.
"Import image" - clear.
"Create app" - clear.
"Add description" - clear.
For further reading, I suggest the Android Writing Style.
The words have subtly different meanings.
Stop means to prevent something from continuing, but not necessarily permanently. E.g. stop video playback.
Terminate means to stop permanently. E.g. terminate process.
Abort means to terminate before completion. E.g. abort file transfer.
Cancel means to make something void. E.g. cancel subscription.
Be a voter > Vote now
Christopher Bryan and Gregory Walton (2011) conducted a study for understanding
if using a noun or verb statement have an influence on user motivation. According to the results of their study, participants in noun group expressed significantly more interest, 62.5%, in registering vote than participants in the verb group, 38.9%.
There's definitely no right answer to the 'best term' to use here. In terms of context, you're correct in that 'Favourites' or 'Bookmarks' don't really feel right.
An obvious solution would be 'Saved' or 'Saved for Later'. You could borrow from Twitter and Pinterest where you 'pin' items (the metaphor mightn't work, but certainly 'pin' evokes less ...
Don't give instructions. Give clear, concise, impossible-to-ignore examples.
(e.g., Bob Jones, Liz Johnson)
The example names that you choose, like the ones here, need to communicate that users are encouraged to enter their "daily use" first/last names, without having to actually type out that direction, which users may glaze over.
I don't find apologies very humanizing from a computer, any more than an automated hold system for a phone network makes me feel like my call is important by saying, "Your call is very important to us! Please stay on the line for the next available representative."
I don't think the apologies are the main issue here. Far more important is that they are ...
The most appropriate is NO
According to one of the 10 Usability Heuristics for User Interface Design by Nielsen:
The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.
When you tell a ...
IF you don't want to use the word device then you could use something more specific like (obviously) operating system. Or just use "Restart your system." "Not compatible with your system" Or don't even give it a name and say "Restart" Not compatible with this OS.
Conventions and the conscious breaking of
The vast majority of people don't have their mouse buttons swapped. Even people who use the mouse with their left hand, often keep the buttons as they would normally be (myself is an example for this). Thus, people who swap these buttons can be considered in UX as complementary personas (people with special ...
Yes, error messages should apologize when it's plausible to do so. People will ascribe human emotions to computers, so the computers should be polite, particularly to users who expect people to be polite.
For example, websites designed for the elderly would benefit from very polite messages both
to show that the site and not the user is at fault
Given today's date, 6/20/2016, I offer my users these choices:
Last 7 Days 6/14/2016 - 6/20/2016
Last 30 Days 5/22/2016 - 6/20/2016
This Month 6/1/2016 - 6/20/2016
Last Month 5/1/2016 - 5/31/2016
This Year 1/1/2016 - 6/20/2016
Last Year 1/1/2015 - 12/31/2015
All Time First Record ...
So the user is interested in the price history of a product? And this part of your website lets them see how much the price of that product has changed between the first date and the second date?
What criteria do they use to pick the two dates? See if you can find a way to tie it to their workflow.
As an alternative, and this doesn't directly answer your ...
Does your system allow users to control their own display name at a later point in time? E.g., once hired, can Robert V. Jones go into some settings panel somewhere and change their own display name to show "Rob Jones" or "R.V. Jones"? (If not, what happens if they change their name legally and want to be subsequently addressed by "R.V. Smith"?)
If so, I'd ...
Undo and redo are really old paradigms, and they usually refer to small actions (like making a word bold or deleting a sentence). What you're talking about sounds like a revert (in version control terminology).
If there isn't a redo option, you could call this "delete my recent changes" instead, and make the confirmation a nice (red) delete button.