Tag Info

New answers tagged

0

I would strenuously avoid coach marks and tutorials. They're mostly not effective; people tend to dismiss them right away and they don't want to read a manual to get started (http://www.nngroup.com/articles/mobile-instructional-overlay/). We've personally seen tutorial walkthroughs mostly fail in usability; most people seem to prefer trying to figure out ...


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

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 ...


1

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 ...


0

Personally, I've always been a fan of reusing the buttons to give users feedback on their actions, and this I think is a good idea. I think what you're aiming for is the right approach, but I don't think the button should revert to the original text right away. Instead, consider changing the text to something like "Resend Email Again" (though it's too ...


0

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.


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 ...


0

There is no rhyme or reason as to the layout here. Consider grouping your buttons into logical groupings, perhaps emphasizing some over others based on priority of use.


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

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!".


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 ...


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

If all the buttons are required to be shown show them as a drop down menu with actions(like the hamburger icon and the drop down using it) and if not change the buttons contextually(which is easy with the basic JS)


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 ...


0

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 ...


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 ...


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 ...


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 ...


0

I am more of developer than a UX person. But I feel dialog boxes without a close button have a purpose. For the most part I like a principle from About Face of don't ask for confirmation. Rather give them a chance to undo. Problem there is some actions cannot be undone and can have severe consequences. This is kind of a data integrity thing but release ...


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(?) ...


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 ...


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, ...


0

instead of using hover (because it's not feasible for touch), I suggest you should implement something like a wizard. Going step by step, the user knows exactly what (s)he is entering. The benefit: You can create hotspots, wherein you can highlight buttons with colour schemes for a few seconds before making them neutral. This way the user will only see ...


1

My solution for deleting things is a button with a trash icon which opens a little popover. I think this is a good solution because: no disturbing dialog, everyone hates confirmation dialogs! confirmation is required. no accidential clicks user has only to read two words, no annoying question red color indicates that it is really deleted, you can empasize ...


0

If you take the MS Word example, when creating new document it gives you the option to choose blank or from available templates. You can slightly change this to say 'blank' or 'copy from existing record'. Hope this helps.


1

I dont have a refrence on research, but definetly there must be one: Referencing desired behavior by location is easier, than by toggling single control state. This means user is more likely to associate left and right with designing and browsing and wont even read buttons in future. In your mind you have this task as "I want to switch design mode" ...


1

After much consideration, our team decided that the best option was to ditch the idea of a button altogether. Instead, in the dialog for creating a new record (which we already had), we now have a field for allowing the user to pick a pre-existing record to copy. In this dialog, we are using the term "copy" to describe what is happening.



Top 50 recent answers are included