New answers tagged warnings
2
I want to challenge your descision to revoke their right to any kind of technical support for a service in exchange for being allowed access to beta or in-development features of said service.
How are you going to evaluated those features if you do not have user feedback?
Secondly, why don't you give them access to technical support? Is it for a principle ...
13
This may be a case of the more you make users work, the less they try. I believe when confronted with a task, like trying to understand some content on a page, users do a quick estimate on whether the effort will be worth it or not.
Too often we present users with extensive content and clicking just to tell them something that they already know or don’t ...
0
Since to go back the user must drag the cursor to the back button why not place a red tooltip there (I guess this is what you are suggesting in the question itself). Something like this
download bmml source – Wireframes created with Balsamiq Mockups
2
Typically in this situation applications will present a dialog that looks something like this:
download bmml source – Wireframes created with Balsamiq Mockups
This is in line with your intuition that a warning that "going back" is unsupported behavior is the best UX to provide in this situation.
Note that it may be possible to support the back ...
7
Other than the obvious answer: "re-write your app so it supports common user actions better" You could try manipulating the browser history using new development techniques (usually outside the scope of a UX answer). Otherwise, a JavaScript alert will only fire after the users have tried to leave the page for any reason, which might be confusing to them. ...
Top 50 recent answers are included
