Tag Info

Hot answers tagged

6

Use specific math symbols, not para-math or pseudo-programming. Some part of your users may not be familiar with math, so provide a description next to symbol. Group similar symbols (less & less or equal) into pairs. Consider using "belong/not belong to set" instead of "between".


4

I like to label buttons with the action they perform where possible. In the dialogue you describe, I would try something like this:


4

Since the phone number input is not critical, popping up a dialog box is bad user experience because you're annoying your users for nothing too important. I would implement it like this: In irregular intervals, have an extra box within the page in a slightly different colour than the rest of the page saying "Just a quick check" as the title. Then at the ...


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


2

A Dropdown with just two options isn't the right way to go consider displaying both the options with radio buttons. Using tabs in a wizard wouldn't be appropriate. Consider something like this . It will be a better to convert the tab into one additional step.


2

A wizard with tabs? Wizards and tabs should be mutually exclusive. As it says on page 179 of the Windows 7 User Experience Interaction Guidelines, you shouldn’t use tabs if the controls on one tab are dependent on the settings of another. The user should have one decision for each page of a wizard –there never should be so many controls that you need tabs. ...


2

1. Is it OK to resize the dialog to accommodate changed content? Yes it is nowadays, providing it doesn't cause the window to scroll offscreen. There are lots of ways to do validation notices, but the approach you've chosen (notify below the field, red, left-aligned) is a very well tested and classic approach so it's a safe choice. The main downside to ...


2

You need to correlate the need of phone number (yours need) with the user's need. Since, it's a job application, you can prompt the message to complete his profile whenever user apply for the job or whenever user wants to get notify about any new opening with mentioning the benefits. If you wants to notify user, do it in subtle way, don't block user's way ...


2

It's not recommendable to use the word Cancel in pop-up/alert boxes. You could use another wording like close or quit. You have several good combinations for the buttons, here is just one (for example, you could change Cancel for "No, stay"): download bmml source – Wireframes created with Balsamiq Mockups In the case you decide to use it, you ...


2

In general, when something goes wrong, software should—in decreasing order of preference: Recover automatically with the most commonly acceptable fix, without bothering the user. Undo can hekp the user back out of a fix they don't want. Offer to fix the problem, with the most commonly accepted fix as the default choice. Inform the user of the problem and ...


2

Firstly, that was an example given in one answer, not a canonical statement of fact. However, I believe that the point that was being made in that answer was that it is poor UX to present a user with options which they don't understand. To extrapolate on that: the vast majority of Windows users will not understand those options, even if you devoted a ...


2

In my experience working for my company and developing user interfaces for automated machines, i've seen that the only case where such windows and dialogs are required is when critical functions are activated and the application must be blocked until such operations terminate. In all other cases always on top windows/dialogs result annoying and frustrating ...


2

It's not appropriate to keep the upgrade notice on the very top, regardless of which other applications you might want to use, while the application in question upgrades itself. Window management and the Z order of windows Your question is about the stacking order, or Z order, of windows. I assume you're dealing with a PC or tablet, since small devices ...


1

You should keep the button labels as short as possible and they should be simple commands. So yes/no is better than long descriptions for each button. However, rather than yes/no, more descriptive commands like discard/keep are preferred. The description should, instead, be placed in the text area of the dialog. Take this example from Microsoft's Dev ...


1

Another way to get around the navigation between projects (when you're already looking at the detail of an individual project) would be to split your page - one part of the page can hold a thumbnail gallery, the other shows the content for the currently-highlighted project, with a multiple image selector and your descriptive text. This prevents the user ...


1

The outcome for the choices given is not fully explained for the non-technical user. It's quite reasonable to expect the user to want to minimise the size of the database AND maximise the search capabilities yet these two options are mutually exclusive. The reason for this is not explained at all. The customise option is not explained either: how will ...


1

There are two scenarios in this question: 1) The user has 'not provided a phone number yet' or; 2) The product owner wants to know the phone number is up to date For the first scenario, it's important to provide a reason why you need this information, (esp. if you can't directly align this with user's needs). So be communicative in the dialog (answer the ...


1

As per the Android guidelines, for every application installed the Play store or Web interface shows a dialog with all permissions that the application will use. By accepting this, you are providing the app permissions to use Push notifications in your application. There is no explicit confirmation made from user like as in iOS. However if you wish the user ...


1

When you download an application from google play it gives you a list of app permissions that are needed. When you continue with the download and installation of the app you essentially agree to let the app use these permissions. Apps typically have a config section where users will be able to control things such as the amount/type of push notifications ...


1

Why not just doing this? If you have the freedom to change a little more the design you can follow a path to completion approach:


1

If you can't change the buttons, I would just widen the textarea to the full width of the box. And I would provide a reason for WHY you want me to give you a reason to delete something, like "We can make our service better with your feedback", or something along those lines.


1

Considering the user cannot navigate to the second tab, keep it disabled. When conditions to enable it are met, enable it and provide a fade-in animation such that the user notices the change. Keep it simple! :)


1

Surfacing new features and 'discoverability' in general are major UX challenges. Don't expect a change log (or any other approach) to completely handle this for you. Users can and will ignore even outrageous modal dialogs. As a general goal, you should strive to make new features naturally apparent to users... sometimes easier said than done. For a ...


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

Have you tested the functionality with your User? It is not difficult or very time-consuming to locate and garner files using the OS search functions and copy and paste them into an appropriate folder. I would be very upset if I had to pogo stick in and out of your upload dialog 20 times to populate a photo gallery.



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