Don't write error messages blaming the user. There is no actual benefit to you from doing this.
In the event that someone accidentally triggers these error messages, you damage your relationship with them. Even if you do manage to tell a single malicious user that you know they're malicious, it isn't going to make them like you any better.
All you're ...
The first thing you have to find out is, if it's really a troll. Your Contact Form and Feedback Form examples have nothing to do with trolls. It's just a feedback message. The third example sounds like a hacker or script kiddie who's trying something, also no troll.
So for the first two examples, choose a error message that tells what to do, but does not ...
Notifications choice often depend on what system you are building for.
If you are building for an existing platform e.g. an iOS app or Android app, then most platforms have guidelines which are in place to keep the use of these consistant throughout all these platforms applications.
Here are a selection of these resources:
Microsoft - UX guidelines for ...
In your case that color scheme is NOT safe for colorblind people. First of all don't forget that there are different types of color vision deficiency. Let's summarize why your image is not safe (to reproduce this just pick two different on-line color blindness simulators):
Achromatopsia: they see only shades of gray then obviously all boxes ...
I would start with different (and larger) icons for the notes in the table/grid e.g.
an icon of a note with a padlock for internal notes
and icon of a chat symbol for external notes
Then I'd consider moving the icons closer together, to make the differences between them more noticeable (to prevent user from only noticing one). Make sure they are not too ...
The system is clear and it certainly will work.
The only thing to note is that customer B might have less probability than initial A to go, because he might have done other plans.
So instead of B being auto-confirmed maybe B should have a period of time to confirm. If he doesn't confirm in that period of time the opportunity passes to C.
In a related point, there is a law in effect here in the US that affect most websites. I'm working on updating content on several large websites for this change.
The California Internet Privacy Bill. Our legal counsel has boiled it down to the following points.
If any consumers of your web service are located in the state of California, you must:
Great question, really!
The problem does not lie in Yes or No. But if the action is Positive or Negative.
"Are you sure to permanently delete System32?"
"Are you sure you want to backup this photo?"
As you can see here, the principle of good design is violated. If you specify Yes or No in the UI of your website/app, you're ...
My assumption is that it's a combination of the following arguments:
Shutting down is a relatively uncommon action (for dealing with your example about getting undesired calls, the do not disturb feature and airplane mode are much more convenient).
There are sometimes issues identifying the intent of the user based on voice input.
It would be very ...
You should consider checking any color palette options using an on-line simulator such as Coblis (http://www.color-blindness.com/coblis-color-blindness-simulator/), which shows you how images look simulating various color-blindness variations:
It is also generally accepted that to guard against this sort of issue, it can be wise to use shape, contrast, and/...
I would say you should explicitly label them as such:
Maybe even do a bootstrap-like popover notification when they hover the green, Client Notes, icon which explicitly states that These notes are visible to the client!
After reading your comment I would like to update the answer to mention that adding alerts, confirmations, Captchas, etc...are ...
You've stumbled across an 'age old' question of feedback
Do we provide feedback if an action completes as it should, or only if it fails? In reality this is often not a user experience question but business decision 'from above'. I expect in the anti-virus example above it is just to remind the user of the product/company and so they think "oh yeah that's ...
Emotions is widely used and expresses feelings, mode and tone of the sender of the message. It’s mostly used in between people communication, where you in a text message can convey irony, sadness, excitement or happiness, which would take too long to write out, especially if the number of characters are limited.
In the more recent years, these emoticons have ...
At a conceptual level an alert is usually a cue used to raise a users attention. For instance a phone may vibrate to send an alert that something requires attention.
A warning is usually related to the consequence of an action (or inaction). A warning can be given before or during an action, but not (usually) after.
Let's says you're running out of battery....
For most commerce sites, you do not want to lead the customer on or p*ss the customer off.
Therefore, letting the customer know as early as possible is the best practice.
If you can determine the location beforehand (e.g. using the methods that @skwotz outlined), then you can filter products accordingly.
But sometimes sites cannot tell where the customer ...
For your responses in your user interface, assume that the user is a genuine user who is making a mistake. They are the only targets for your user interface. For security reason, make sure that you don't give any hints to malicious users how to get around security. For example, say things like "your username or password is incorrect" and not "your password ...
To answer the question in the title: don't. Treat data trolling (invalid data input) for what it is: invalid data input.
The simplest way to keep people from 'trolling'? Don't allow users to break things. If you do, users will play around when they really shouldn't.
For the form UI: don't allow the user to click submit (grey it out) unless all forms are ...
Let's take a look at what other applications do
Applications on macs and windows (from what I recall for windows... been a while since I've used a windows machine) prevent the user from moving forward before they decide whether they want to save or discard changes.
The reasoning behind that is because if the user leaves the application, then a modal/...
Always give users control
Our inboxes are overloaded as it is. You're right to worry. You have to provide notification for those who come and go, but you can't force on the regulars or people who end up linked to a popular discussion.
Stack Exchange provides a good pattern
A checkbox to activate email subscription:
And in-line settings to control frequency ...
It varies, but for English language....
Generally the time taken to read a flash notice will vary according to the complexity of the information, length of notice, and focus/distraction level of the user.
That said, I tend to use the following informed approach:
1. Flash notices should be short
If a notice is longer than about 1.5 lines, it likely too ...
You've detailed the actions to the user in the modal box, what you are assigning to the action of clicking outside of the box is a presumed action, as such, you simply cannot 'presume' the user will know this.
IMO this would result in a poor user experience.
A better prompt would allow the user to cancel the modal box and return to the application or ...
That dialog is very confusing.
It can be interpreted two different ways:
The application is warning the user that pressing the back button has initiated a quit action. Pressing 'OK' will acknowledge the warning and proceed to quit. This leaves the user wondering if there's any way to not quit.
The user needs to press the back button a second time ...
It depends on how many notifications you are sending, how frequently they are sent, and how relevant they are to the user at the time.
If you are only sending one or two notifications a day (excluding chat notifications) that are likely to be relevant to the user then it's fine to leave it up to the OS/browser to disable notifications if the user doesn't ...
Display the upgrade message as they did not make an error. Allow for a CTA to upgrade.
Spotify does a simple job of this. If I try to download, I get a top level banner, info style, with call to action for Premium:
The animation pushing down the UI, and the color contrast make it easy to notice. It directly references the action I attempted: Download, and ...
I'm currently working through a set of very similar problems so I've been giving this topic a lot of thought.
1) I see 0 benefit in displaying a list of "Read" notifications when notifying the user of new activity/events is the intent here. I'd focus solely on "Unread" notifications and have a control that can let the user access older "Read" notifications ...
First of all, never count on users to read anything. Not. At. All. They won't, and by the time you are explaining to them that the label was Right! There! On! Their! Screen!, the damage has already been done.
Consider making the micro-interaction for composing a customer-visible note strikingly different — and slightly more difficult — than writing an ...
I'd advise against asking "on initial startup." General consensus seems to be that users hate being asked to rate apps with a pop-up (regardless of the content), and developers risk negative ratings for asking too early, too often, or too intrusively.
This is especially true:
Right after start up, when the user wants to accomplish something
When it ...
How critical/catastrophic would this operation be?
Trivial: no prompt needed; rather, provide a simple undo button.
Non critical or easily undone: prompt near the button, as to not annoy users too much and make them lose focus.
Critical and can't be undone: centered in the page