Tag Info

Hot answers tagged

4

I think this hinges on whether the order of the playlist has meaning. On a 10 track CD, the songs are meant to be played in a certain order. But a user constructing a playlist with hundreds of songs is not thinking "I want to play all of these songs in order". If the latter is what you see as the common use case for your software, I agree with going back ...


3

The only time I can think of when no close button should be there is when "Cancel" action is not acceptable, e.g. the user must make a choice. This is often connected to popups that isn't caused by user action. For example, the system must be restarted and asks the user when the system should reboot. "Now", "In an hour" etc. Letting the user close that ...


3

The main problem seems to be the amount of buttons not the kind of their appearance. The goal is, that your user finds the right button fast. A visual hint would help, but if the icons ar not self-explanatory, the users would have to learn their meaning which only helps if they use this form often. Anyway, each time the user has to scan all buttons to find ...


2

I would recommend going with a simple approach like this download bmml source – Wireframes created with Balsamiq Mockups I would recommend putting the archiving or withdrawing option as the primary call to action as you want that to be the primary interaction and not have the user be accidentally deleted. Since there is some confusion about ...


2

Maybe you should separate the target and the actual pointers to make it more clear? Sometimes (I for one) spend far too much time trying to do things too minimalistically - as in this case; get two values to show up on the same area instead of just separating them...


2

The problem here is the design itself Besides the problem you have encountered, this design is just plain confusing, and it requires a lot of effort to look at and figure out what the actual and target levels are, since they aren't always in the same place. Instead of displaying all five levels, only display two boxes, in two columns: the target value and ...


2

As with the response by Shano, I think this would work better by moving the feedback outside the button. I would also disable the button. This would avoid people double clicking and accidentally sending multiple emails unintentionally. I would also want to confirm what the goal is with the delay, Is it to prevent accidental multiple emails, or to prevent a ...


2

It's not 100% clear from your question whether the product exists yet. Register your Interest would be good if you are collecting leads for a product that doesn't exist yet. Request a Quote is pretty standard if the product exists, but further contact is required for the sale. However, it implies that the price is unlisted and negotiable. If the price is ...


2

Try re-phasing your question this way... As a user, what are they trying to do? Are they trying to create a new item? Or are they trying to view a new item form? Even though they are technically going to a new page, the end goal they want is to create that new item. The form page is just a sub-step required by your app. To label a link along the lines of ...


1

I would use a radio button for this interaction. It allows you to default to the safer of the two actions. It also allows the user time to consider the two options and think about the difference before making a selection. Sort of verify before click rather than after. Keeps the interaction together on one page. For the wording I would use delete user and ...


1

In this case it sounds like one option is just an extension of the other (they both remove the user, but one also removes the archive record)... You could use a checkbox to confirm that second action. download bmml source – Wireframes created with Balsamiq Mockups You could also use a popup to accomplish the same thing... download bmml ...


1

The answer, as in many UX situations, is "It depends." But seriously, it sounds like: there are some areas of the system in which the Cancel button and the Remove button do different things, and need to be differentiated from each other. there are some areas of the system in which they do pretty much the same thing. First, we'd need to find out whether ...


1

In my experience, Remove and Cancel are two different actions and should be treated differently. Remove implies a destructive edit (removing data that has already been created). Cancel implies a non-destructive function (such as closing out of a save modal) or exiting a data creation flow prior to saving the data to the database (such as at the end of a ...


1

Buttons initiate a process: Submit, Cancel, Save, etc. Submit buttons can be used by the keyboard to interact with a server, mapped to the Enter/Return key. Links are anchors that connect one HTML document to another. This is a subtle but important distinction. If hitting the button does not save (Post) a current new item (like Save & Continue) then I ...


1

I agree with nightning's answer, but also think that it doesn't really get the point across. The question shouldn't be link vs button, especially for a web-app. The principles behind both are slightly different but often the same these days. A link is as it sounds, a door to a different page. A button is more like an elevator button...you'll get to the next ...


1

Why not move the animated spinner outside the button? You could place it immediately to the right of the button when clicked. When it's sent, replace it with a green tick and text 'sent'. If button is clicked again, the 'sent' text is replaced with spinner and it goes again. Just an alternative idea that might look less confusing.


1

First leave the text, and focus on the color- Principle: Use alternative color and Make the button big. Second, come back to the "call to action" text- You should be transparent with your customers. The simplest text should convey "Subscribe to product alerts!".


1

It might be best to try an alternative layout for the buttons rather than icons as knowing what an icon means outside of the staple well known ones, for things like Play, Pause, Save, Delete etc. is not always easy. It might be more worthwhile spending time on a good translator and using something like i18n for internationalisation.


1

(A) has the problem that the message is about saving, but the Cancel function cancels the navigation. (B) does not have the option to back out, so it does not support your scenario 2 ("...accidentally..."). (C) suggests an action which is rather improbable (assuming most people want their changes saved :-) If I only had these choices, I would add the ...


1

Removing the [X] button should be avoided at all costs since it is the go to button if you don't know what to do and want to cancel your actions. That said I have had to make a few of them in the past. The reason was that we were building a new UI on a very old piece of software. On 1 or 2 occasions the software needed a response from the user in such a way ...


1

I want to start of by saying that I loath modals. I do know that there are certainly scenarios where they are good and necessary, but I really don't like them on principal. That being said, some of the examples given, I would argue, do not justify the disabling of the close button. A close button is a very known and comfortable escape hatch. Depending on ...


1

Personally, I think Microsoft's guideline makes little sense. A typical dialog requesting a decision from the user give buttons for all of the possible actions to take at that point (ok/cancel, yes/no, save/don't save/cancel). On most dialogs, the close button doesn't give the user additional "control"; it just provides a duplicate way to perform an ...


1

If you add buttons with arrows that points up and down, those would be the ones that traverses the list (if you are on song #500, one step up would be #499). The right and left arrows would in that scenario be history buttons - meaning that the right arrow would (almost always) be superfluous. This would map better to the interface, since the list is(?) ...


1

i would suggest going back to the previously encountered song (#1). it would be something to do research on, especially with your specific app in the case that it differs from others, but I would assume that a user is more interested in going 'back' to what was previously encountered as opposed to going 'back'wards in the sequencing of the playlist, ...


1

I would have the Create button, near the top of the page (perhaps in a fixed/sticky bar, so always visible) as you mention. Then if your design is a table of items which can each be read, updated or deleted. Have a column to the far right, with buttons for each action arranged horizontally. These could be simple text links, buttons or icons.


1

Based on the information given, your design seems like a very good one. Being able to perform actions without scrolling back to the top of the page is an obvious benefit. Functionality should not be dictated by what is easiest to develop. Within reason, development should be driven by design, not the other way around. And your proposed design is ...



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