Hot answers tagged interaction-design
17
I cannot comment on your user test results since I do not know your parameters and scenario.
But, talking about gmail's new email input method. The advantage which desktop email applications had over the web based ones was, while composing the email (in a separate window) you could freely browse older emails and look into content you might want to refer. ...
8
Radio buttons will be the most clear, as far as indicating that the options are mutually exclusive. Your Option 2 check box is very unclear. It looks like you can do a search with or without promotions, but from your description you're either searching for reservations or promotions.
I suggest something more like this:
download bmml source – ...
6
As far as I know, all applications should employ this feature. The menu label when clicked first, opens the menu and when clicked once more, closes the menu. This is the default behavior to close the menu. You can have other behaviors like, closing on losing focus or closing when clicked out of bounds.
The clicking to close menu acts as a nice 'undo' ...
5
You are trying to deal with concurrent editing, and unfortunately there isn't any easy solution for this. The common ways of dealing with it are:
Lock the record when someone starts editing it. This will prevent a second user from editing a record that is being edited and should inform them that someone else (possibly a name) is editing that record. ...
4
They are useful during pure media consumption like viewing images, videos, etc.
Regarding the issue of educating the user of their usage: the current standard implementation is quite good enough. Display the controls and additional data when opening the content and then remove them after a few seconds. This tells the user there is all the other information ...
4
Case 1: You do not have a timer and the notification stays till it is manually dismissed.
There is nothing wrong what-so-ever with this approach. You display a message for undoing and it stays till the user has read and consciously dismissed it. Great persistent feedback and lesser chance of missing it even if you are distracted somewhere for a while. The ...
4
The general rule is that if you can achieve the same result with less user interaction, you should do it.
Infinite scroll is one of the clearest ways of handling this. When someone has scrolled to the bottom (or near the bottom) of the screen, it's a fair bet that their next action would be to load more or go to the next page. So is you load more ...
4
Why should users make this choice when searching? As the form fields are the same, use Option 1 but without the tabs. That way you remove an unnecessary choice for the first step.
Instead, you can offer the option to filter the results on the result page.
You could use the two tabs there, selecting the more common one by default. Or you could provide a ...
4
Users typically want to see the most recent activity first. Think tweets, online banking transactions, news updates. It makes it easy to see what's new since you last checked.
With conversations, it's different because there is the context of whatever message came before and after the one you're looking at. It's a similar situation to what you see in ...
3
Some ideas:
Join the buttons with some sort of bar.
Crank down the color. It's hard to spot what's selected
I think the transition from saturation = click me to saturation = currently selected option is confusing. I'd represent the transition with two different metaphors.
Here's a quick idea:
3
The simple answer it that you should place an advanced search option everywhere that you have search in your app. The prime reason being consistency.
If it's available for the search on one page, but not on the next, you are going to confuse users. People think relatively, and so they associate advanced search with search. When you then leave it out, ...
3
What you are looking to do is reduce the results.
The key to this is to provide the same tools that users use for browsing in the search result, with a few tweaks to make them relevant. Avoid thinking of it as 'advanced search' as that's not the way users think - they just view it as one experience.
With the shopping sites I have worked on the common ...
3
Skeuomorphism did indeed become very fashionable with Apple and you are right that the purpose was to give the users a connection with objects of the real world by adding these textures.
The use of skeumorphism is a matter of taste. Almost like if you use monochrome designs vs using the whole palette. However, when using Skeumorphism you need to find a ...
2
This is poorly implemented example of navigation. A menu is NOT A WINDOW which should stay open unless closed. Menus are set of commands and while searching for one, I open few menus before finding what I am looking for. That means every time I open a menu, I expect it to close when I click outside or click on a different menu. So the example you are ...
2
The answer is simple: because the designer did not think everything through. And the programmer implemented the design without further thought as well.
Most users, while working with computers, think this way: if I do something to make things happen, doing this very same thing again should reverse things. Possibly because such behavior was introduced in ...
2
If you are using sliding animations between screens, you should stick to the convention that pushing a new view from the right = forward, and from the left = backwards. Otherwise your sliding animation not only looses its purpose, but it actually then causes confusion by implying something that isn't true.
The second part of your question is more ...
2
Only the currently active player should be able to pause the game, to prevent any other people interfering with their turn.
If quitting brings up a menu that can interrupt the player whose turn it is, then only the currently active player should be able to quit the game. If that isn't the case, then any player should be able to quit the game.
What is ...
2
I would say the controller of the currently active player - all of the other players are 'paused' anyway.
Also, when Bob is about to cream Joe, Jane and John, it means that Joe, Jane and John can't rage quit as easily - or make it a pain for Bob to win by constantly bringing up the pause menu.
2
I saw this link on Dribbble.com that looks similar in the look and feel. My initial reaction is that depending on the average number of different time entries, the best thing is to go with a more flexible approach that separates the two parts of the interface. The first part is to show the overall timeline, and the second part is to allow users to provide ...
1
There's one big limit to on-page dialogues: They're always going to be covering up part of the page
Unlike having two actual windows, your dialogue can't be moved outside the browser chrome. You can't move them side-by-side (like the snap feature in Windows), for example. It'll always be covering something, somewhere. Arguably this can be more annoying than ...
1
Answering to your question "Why is this not being used more widely?", I think it has to do not only with Google being the first one to do it, and do it right, but also with technology.
We have web applications that are still using tables for non-tabular data, applications that haven't changed in years. A dialog like this requires, at least, some ...
1
The dialogs are not modal, so one can compose multiple mails in parallel by clicking Compose again. All parallely composed mails are auto-saved to drafts, they are undockable and minimizable in the window, so one can still browse and answer incoming mails in the also GMail-style "conversation" view.
As you see, these dialogs are quite powerful. The reason ...
1
Pausing should be in the hand of the active player.
Depending on the type of game you might or might not want to allow the player to quit during someone else's turn.
It helps in notifying the current person if he needs to change his strategy based on that decision, rather than taking all the measures only to find out that his target quit.
However, if you ...
1
Since the user will be reading in downwards direction for each article, it would make more sense for each next article to be below the current one. This way a user can just keep on scrolling to go through the article, instead of switching downwards, sideways, downwards, sideways. One app that does this well is Reeder on the iPhone, but there are many others. ...
1
There are already usage patterns for this type of interaction that are standard on iPads. Granted, none that I know of with a tab bar, but that shouldn't change the principle at all.
I would recommend not doing this, but rather having an optional overlaying sidebar in portrait mode, which then becomes an always visible sidebar in landscape mode. The Mail ...
1
Boolean logic is definitly not user oriented
For instance it is very hard to understand that :
download bmml source – Wireframes created with Balsamiq Mockups
You should reconsider your approach if you do not want confusion. I know you do not want confusion. The thing with nests is that they do not act like Venn diagrams. They are not visually ...
1
Limiting the time for undoing actions limits also the undo feature to 'oops...' functionality only/mainly. It will not let user undo some actions they performed in past after getting some more information about whatever is related to this action, or the element the action was performed on. So having an endless undo feature is a value from user experience ...
1
Usually a drop-down menu disappears when the user clicks anywhere BUT the drop-down menu.
That is what a user expects and it really annoys her when she clicks outside the menu in order to activate another action and it does not close the menu.
1
If the user doesn't need to worry about it until it's time to click search, why not just end the single form with search reservations and search promos buttons. If it's somehow relevant, you could even use a representative icon in each button to reinforce the distinction at a glance.
1
If your site is also to be viewed on mobile devices, you should use "Load More", in order to allow the user whether he/she would like to spend more of his data plan's bandwith.
Also, this depends on the type of data you will present.
For casual data, and on desktop/laptop devices, auto-scroll is ok.
For business data, always use "Load more", so the user ...
Only top voted, non community-wiki answers of a minimum length are eligible
