Tag Info

New answers tagged

0

How about using bar graph design, will be more intuitive to click and match your theme as well


0

You can try doing a glass like effect button. Something transparent glossy effect.


2

If the "more main" functions are all related to adding things, you could have the FAB expand into a collection of smaller FABs that give more options. Tapping on the original FAB a second time could execute your primary action. Google's Inbox app demonstrates this, as do apps like Tumblr. Alternatively, you could change the icon on the FAB to be something ...


1

Maybe would you use something like apple scope bar?


0

The list you showed is designed for items that are quickly/easily recognized like the days of the week. Survey questions aren't that type of content. Don't make users scan a list, find the question, read the question in the list, find the corresponding button, check the button's state, tap the button to change its state, check the button's changed state, ...


0

Toggle buttons are an interesting alternative to radio buttons and in this particular case it would look very similar to what you have and would take just about the same amount of space. In that respect there would be little difference. One of the differences would be that the toggle button is a bigger target than the radio button. Of course toggle buttons ...


1

Consistency First, let's define consistency (within desgin context): Things that share similar semantics should be presented or act in a similar way. And its misuse Now consistency is one of the most often misused concepts in design, for two reasons: Designers adhere to the guideline ignoring the actual problem at hand. In other words, the ...


0

If your dialogue is titled Client selection or something similar, there is no need to add more info on the button. I think a button called Validate will do. @EDIT : Since it's not a validation, try Add client button ! ;)


1

Another thing that might work is to use tabs which mark the Summary Stats rectangle... then automatically switch context over to Specific Stats as needed in your example above but leaving a clear way back for the user...


0

My general answer is consistency; Consistency can prevent user confusion and not make the user think. Muscle memory will remember where the buttons are. However - is there a reason why your users would expect the buttons to change? Is it something they might expect? Why not try a lowfi prototype and see how your users respond - you should have an answer ...


1

Great question Mattias. I think you should lean toward consistency. In recent usability testing on our site we found that everyone accomplishes tasks differently and in a trial-by-error fashion. Consistency from page to page helped our users maintain a sense of clarity and made things appear more intuitive, even if it was an action they never performed on ...


3

You would need to test it out but I believe that one of these buttons would more clearly communicate the described action to the user...


0

In principle it can be good design Benefits Highlighted buttons present a clear call to action or default action for users. For example, it can be frustrating to users to pop up a dialog box and not have a primary button, because the user has no indication for the preferred flow. Similarly, if a user fills out a long form and then is presented with 3 ...


0

Labeling the button "back" may be general but that's the appropriate label. From your description, "Summary stats" and "Charts" are not related with each other. In this case you can consider a separation between them like the below. download bmml source – Wireframes created with Balsamiq Mockups In these cases the user will know that ...


0

I am feeling lucky : How about a simple arrow icons (<) on the right hand side or as an icon on the left (Back icon) Specific Stats . Nicely done visually. Instead of even writing Back. I feel its pretty clear even if users did this once. I think "Back to Summary" is ok. (are you having space and visual clutter issues then my suggestion is don't try ...


-1

I would suggest a pop-over that has a 'close' button for the detail view. Otherwise, if it's purely desktop, could hovering the table data expose the detail info?


0

Apart from sensitivity, "abort" by itself is open to too much interpretation. It is often used in circumstances where the user is able to repeat and action and so it's not as final as discussed in many of these answers. Even a file transfer can often be restarted. Considering the immediate effect, use Stop, Pause or Interrupt. You may have some context ...


0

@chris has the right idea. I prefer the 2nd option but with stacked radio options so there is no confusion over which button applies to which label. It also more clearly makes each filter step look self-contained.


2

My instincts tell me that while not a big deal in general, it would be prudent to use an alternative if you can think of one. Words differ not only in the potential severity of an unintended meaning but also in how (un)likely it is that someone would think of these unintended meanings in a computing context. Examples: kill is problematic because of its ...


0

Sorry this is only crude...but just separate out the different filters with a vertical rule. The first ones and can then be the radio either-or combo you're after with the next section clearly being an individual option. download bmml source – Wireframes created with Balsamiq Mockups Another way would be like this: download bmml source ...


9

Historically, the Abort/Retry/Ignore question in MS-DOS was a result of an I/O subsystem which had no way of reporting problems from the disk sector level through the file-system level to the underlying application. If an application asked to read some data from a file, and block 1571 of the disk was unreadable, there was no defined mechanism by which DOS ...


0

I once called a state of a collection of data (visible in a diagnostic app) "Stillborn". This turned out to be too creative. I'm not a native speaker of English and the intended meaning was "Staging finished, state of data invalid or unknown, further processing not possible." As soon as the app was released I received strong pushback from ...


4

Yes, avoid using it. Probably... Some perspectives: Developer language vs user language. Abort and Cancel may have nuanced differences to a developer but to a user, factors like familiarity and friendliness are a lot more important than accuracy. An extreme example of user-language vs developer-language is placebo buttons which do absolutely nothing ...


13

As a former officer in a pro-life political action committee who is also a software developer: I never found the use of the term "abort" in a software product offensive or disturbing. To "abort" a process is to kill it before it has a chance to complete its intended operation. To "abort" a baby is to kill it before it has a chance to be born. We regularly ...


47

Are the listed words really synonyms? I cannot provide any references now (possibly because many software developers/producers do not consistently follow the distinction, either), but my impression is that at least abort and cancel are slightly different: Cancel sounds pretty much like a routine operation. You can cancel something before it has really ...


38

The words have subtly different meanings. Stop means to prevent something from continuing, but not necessarily permanently. E.g. stop video playback. Terminate means to stop permanently. E.g. terminate process. Abort means to terminate before completion. E.g. abort file transfer. Cancel means to make something void. E.g. cancel subscription.


1

Like Matt mentioned abort is a more of a technical term, so whilst we would use it everyday, it's not quite laymans enough. Though saying that, it really depends who you are building it for, if it's devs thats fine. If you're making it for a regular person off the street, they would eventually understand "abort" means to stop the process, so why not use the ...


23

Like everything, this will depend on context. However, "Abort" is one of those 'computer words' that isn't normally used by people in everyday conversation, along with things like "terminate" and "submit". It's one of the reasons that in the past, people had to take computer literacy courses in order to understand technology. Thankfully, User Experience and ...


0

Mobile somewhat blurs what it means to "close" an app. Conceptually, apps are never "closed"; they're just "put away". When you exit to the home screen or switch to another app, the previous app is suspended. It might be kept in memory, or its state might be saved to disk and its process terminated. To the user, in theory, there's no difference, because next ...


2

I will present an alternative view to tohster's definition of what X should do, based on what how I think your average user will interpret it. Your average user's mental model of how a computer works will probably not contain a sharp distinction between close/exit/quit, instead they are likely to have one "favourite" term that they use for all of these. I ...


2

CTA and Buttons Call to action buttons appear in any given workflow to represent and enable completion of task priorities, as such, they are always distinct graphically as well as semantically; a verb is used for example "view" "download" etc So having four buttons in a row creates a situation where CTA buttons are competing for users attention as well as ...


3

When it comes to me, I feel really frustrated when the x button doesn't close the app. Has happened a number of times with Skype. Although, when I retrospect, I don't feel quite disturbed when, instead of a "x" button, the app has an "arrow pointing bottom right" to indicate it's still going to run in the background or will be minimized to the system tray. ...


9

It means Close. Skype’s is a poor design. Use the correct button for your use-case. If your program cannot be closed, or at least non-trivially, don’t display an X at all, or disable the button. Replace it with _, which is the icon used for minimizing. Hindering attempts to close your software makes you look awful This behavior is one strongly associated ...


18

X has never meant exit, but there's a reason for the confusion X has historically been overloaded to mean two different things: Delete an item. For example: Close or Dismiss a window. This is not the same as exiting an app but historically, hitting the X button almost always resulted in an application exiting, so that is why users sometime confuse ...


3

The X symbol can be used when canceling or removing something. In terms of an application's or modal window, the X should be used to close the program or modal by convention. Xs can also be used to remove items from a list, delete something in some circumstances (comments come to mind), or otherwise cancel something. As such, minimizing or another action ...


2

The answer to your question is, it depends upon how the user uses the software. Like other user-interface questions, it depends on the use case. Many of those applications where the close function only minimizes the application do so upon the assumption that the value of the software only comes if it is running all the time. Looking at Skype or Hangouts ...


15

A cross should always be used to close something. The problem is the meaning of closing. One thing is for sure, closing is not the same as minimizing. Your example for Skype in Windows is not correct. Close button closes the window, while the minimize window button minimizes the window, but doesn't close it. Therefore they don't do the same. On Mac OS, ...


0

People often find it annoying that when they click the cross, it's minimized but not quit. If it's moved to the tray, however, they don't find it annoying. Most people don't care whether an application still runs in the background, as long as their taskbar isn't cluttered with applications.


0

Make the change option explicit Eg if option 1 is the existing choice and the are 4 other options Layout would be You current choice is Option 1 (x) Change to..... Option 2 ( ) Option 3 ( ) Etc Makes change explicit and reduces cognitive load How you choose to present will depending on your programming overhead(eg sort order etc) Also by making ...


3

The table is distracting because of: High contrast between the buttons and the tables. Grid layout of the buttons creates an unfortunate grid illusion The palette is visually distracting: you have banded rows already, and then are superimposing a saturated darker blue. That's a lot to deal with when the eye already has trouble navigating a complex table ...


0

I'm not sure I have understood your problem, anyway I see 2 solutions: Use a checkbox like confirm option 2, the user will be forced to check it (modern browsers will add a prompt if the required attribute is present) . This is seen on many website where you have to accept Terms of Service to complete an order, etc. Use <input type="submit" ... > or ...


7

Buttons tend to convey actions, while it looks to me more like these are navigation links. Showing them just as regular links (following whatever style in your app) would be probably be much less imposing both visually and as an action to take. You can also take this a step further, and provide some more useful information instead of simply displaying ...


3

Are all 4 buttons equally important? It might make sense to have the main action as a full button and tuck the rest into a button dropdown. It'll make it easier for users to tell which is the main action and still have the rest be accessible is a touch friendly fashion. The second thing you can look at is button color. The blue is very strong against the ...


2

The simple answer is to use a combobox like the following: download bmml source – Wireframes created with Balsamiq Mockups


0

On Facebook, the like button is a good example for a toggle button. On Facebook's Android app, the like is on a button and it's a grayed when off and highlighted blue when on. See screenshots below. Basically, I agree with them - emphasize the positive and don't mess with users' brains (minimum change). I'm not sure if it's a good way for color blinded. ...


0

If you need the user to change the selection, disabling the save/submit when the user wants to retain the selection may not be the optimal experience. Some alternate strategies would be: Make the button show Save, and then Submit so that if the user wants to retain option 1 there is an explicit confirmation. If the user wants to change to option 2 there ...


1

This is OK and acceptable behavior. BUT: common alternatives are: Allow the user to press save. Disabled buttons can be frustrating to users, and after all, there is no harm done by just re-saving the existing option. This also fixes an awkward case where the user selects Option 2 (enabling the save button) and then re-selects option 1 (do you then ...


0

I am going to consider all text as Lorem Ipsum, for I can't make anything out of it. This gives me a great opportunity to look at the design pattern without getting influenced by the textual content. First of all, you are placing different visual styles together and expecting a one size fits all answer, which I believe will not be possible. A couple of ...


0

Button animations serve a different purpose Observations: The purpose of the animation is not to draw the user's attention, but rather to provide feedback to the user. This is sometimes called a clunk: a clear acknowledgement to assure users that you have noticed the interaction. In the physical world users live in, interactions provide feedback ...


2

Generally, icons should be sized and aligned relative to capitalized font. Text should also be vertically centered in the button using capitalized height. This is because icons and leading capital letters in captions have the most visual mass so the eye reading left-to-right will be most comfortable for those elements are vertically centered. Here are ...



Top 50 recent answers are included