Tag Info

New answers tagged

0

Well, what about putting a notification with the number of attached files below the email body, followed by the "attach" button, and then followed by the "send" button? That way is impossible to miss! I think all the problem comes from bad possitioning of the elements: If there is a top bar, the "attach" button should be the FIRST thing a user sees, and ...


1

Setting a max length for the fields would be advisable rather than changing the size depending upon the longest entry in a database. For instance, the "Contact name" field can be set to a maximum size of 200 characters. This would help stabilize the alignment of the form that you set. However, if that is not possible, you can use the, "one field per row" ...


0

It seems like Windows OK/ Cancel convention has done a lot of brain conditioning for users. So usability tests would certainly come out with lots of people looking for an OK button on the left, Cancel on the right. But that doesn't change the most basic instinct of someone who is interacting with the system without any pre-conditioning. My basic instinct ...


0

Your UI only allows for repeating events by days. You need to add the ability to repeat within one day. Perhaps something like this: Default state: Repeat: ( ) Daily ( ) Weekly ( ) Monthly ( ) Yearly ----------------------------------- [ ] Multiple times during the day You can still choose to repeat the ...


1

You must have a clearly marked exit (Jakob Nielsen - Usability Engineering). You should have two buttons labeled "OK" and "Cancel". Do NOT add an "X", to avoid confusion.


0

You should try to reject possible invalid entries before they get stored to your backend. For the simple reason that no additional controls are required and you can do this completely without any additional user interaction. And as you're saying that it would solve 99% this way and it's a monkeypatch after all, this has to be your first step. If the ...


4

I'd suggest you go with the empty item. For two reasons: To be consistent with your criteria options. Why should a user have to leave the date fields empty to get the complete range but have to select an option when it comes to types You usually refine your search by applying filters. Selecting "All" does not refine your search result whereas selecting a ...


3

I associate "search" with a more open-ended query, almost always involving a text box input (though not necessarily keyword search). The process you're describing I think is more "filtering". I would use a filter icon (a funnel) as opposed to a search icon (magnifying glass). I also really like "Show Matching ...". Definitely not "Find", though, as that ...


1

Non-sensitive data can be stored on the users computer. Local Storage, cookies, whatever mechanism you find appropiate. have alternate server or alternate mechanism of sumission are all possible solutions. Thing you should think about are : Public computers. People may be filling the form on another person or public computer, saving data in this scenario ...


3

I am for the version on the right. Here's why, from a Typographic, Design Element, and Human perspective. From a Typographic Alignment Perspective In the examples I show, I have stripped the input box so you can see it purely from a typographic perspective. Visual hierarchy looks like this: See me first - See me second See me third - See me fourth ...


1

You could use a cookie for the data or store it in a browser database via html5. Even flash cookies might be a workaround. It depends a little on security aspect of data - I wouldnt store banking data offline - and the browser settings. You might find some more ideas if you search web for techniques for evercookie and mobile offline. And the user flow: ...


2

Maybe the button could say, "Show All," before any options are selected, (or if no options are selected, if that's a possibility.) Then when an option is changed, change the button label to say something like, "Show Matching Records." I think the, "Show Matching," label is appropriate in this case, because your users are trying to match the selected ...


0

I'm very late to the party. But I'd like to offer my own solution. That is: using a popup window (aka overlay, modal) to display the checkboxes and let the user select multiple values. The popup window is opened when a user clicks on an edit link on the main form. When he's done selecting the values, he can click a DONE button, which has a click event, a ...


0

Search Disable (gray) the Search when the execute When they change an option or clear then Enable Search


0

further to what Michael has said about consistency, I think it's important to analyse what the modal window is asking and ask whether it really is so important that you must break the flow of the page and force the user into interacting with another interface. Is it appropriate to force feedback? It sounds dramatic, but that's what a modal window is. If not ...


7

In most cases, forms are made of native elements and the look and feel is therefor (ideally) determined by the operating system. Mac OS has a different way of showing something is disabled if you compare it to windows. Here are two text fields of Windows XP and Mac OS X with native behavior: vs. I would advice you not to change this behavior for several ...


11

Generalising between platforms I would go with the following basic guidelines, they further emphasise a disabled field with a grey background. Normal (with a value) Black text, white background, black border. Normal (with a placeholder) Grey text, white background, black border. Disabled Grey text, slightly lighter grey bg, grey border. E.g.


6

Some things I have seen done before in this scenario: Make placeholder text green instead of grey (user input is in black) Placeholder text is in italics (user input is in normal text) Put angle brackets around text, eg. < your name here >. (This one is somewhat "technical", i.e. something a programmer is more likely to understand) I would suggest ...


2

I suggest a grid so the user have the choice to focus on one phone at the time (vertically) or on the features (horizontally) download bmml source – Wireframes created with Balsamiq Mockups


0

I can think of two ways of doing it. The first is to put all the lines into a single table, with a column for each phone line. That is, the feature list at first looks much the same as now, but with the checkboxes &c. on the far right instead of the far left, to the right of the prices. The "Phone line: One" message would also be at the far right, atop ...


1

I suggest progressive disclosure on this issue. Do not disable and enable them but instead keep them hidden until the approriate selection is made in the form. Then show them the field. http://www.nngroup.com/articles/progressive-disclosure/


1

Registration should capture only the minimum required details. But if you want to still capture more details, then you could get them first confirm their email id. The other details that you would like to capture could be done say from their profile page or say the account page.


0

As an enterprise UX designer, I have come across this many times. The short answer is preset the radio button by default if null is equivalent to one of the choosable states and the default application state matches the choice. If not, you will have to dig deeper to make a decision. Here is how I would approach the decision. I would ask these questions: ...


1

Of couse integrated payment form is better once you handled all possible cases like user payed, navigated back to enter more info on prevoius step and then navigated forward etc. It is not only about UX. Its about security, trust and technical problems. To accept payments inside your webside some security procedures have to be applied. For example PCI DSS ...


1

I am a bit confused by all the people suggesting this is about AutoComplete. AutoComplete suggests a completion of what you are typing, eg: Google suggesting search phrases. That is not the same as showing search results. I think conflating the two and the fact that a search is taking time is going to cause confusion. I like the idea of a little search ...


0

It's actually pretty common these days for forms to show correct/incorrect data entry as you go. Usually I see it in the form of either a green check mark or red X showing up on next to each entry. Usually it either happens while you're filling the field out, or as soon as you move on to the next field. It definitely makes it easier to fill out a form if ...


0

I suggest using multiple activities. You could check the form after every activity and make elements bigger which makes your UX better. This way there could be +/- 5 inputs in one activity. Once done the user could click on a nice big next button. (Since they have never used android before this makes it easier.) The activity then checks the data and if ...


1

Even though options 1 and 2 are generally speaking safer, Facebook's approach relies also on a wide range of extra security options the user can manage via your "Security" panel: If you combine the "infinite" approach with these advanced security options and an https connection I think you have a solution that is safer enough in most (not all) cases. ...


1

From what I understand, you want the user to be aware that the TaxCode field is a autocomplete field and a search is being performed as they type. In my experience, making the field a drop down with auto-complete filtering has worked. I'm assuming that the values in Tax Code are not random user generated values and that the value entered can be one of a ...


0

This seems to be more of a security question than a UX question. If I as a user don't care if the account is compromised, I'd certainly prefer that I never have to log in (my yahoo mail account that I only use for fantasy baseball is incredibly annoying in this respect because I have to login weekly if I want to make changes to my lineup). If it's my bank, I ...


47

I would suggest a miniature progress wheel at the end of the input that only displays once a search is going on. I've seen this behavior before (I believe on user name boxes) and I believe that progress wheels are so clear that everyone will understand that something is going on. Once a user types, hide it briefly (or grey out to reduce flicker) and then ...


11

If I understood you right, then you are practically working on an autocomplete field. The standard for those is to offer search results like with a dropdown on the bottom. Therefore the easiest thing would be to add searching... as first item in the drop down whenever a search is performed. Maybe animate the … / three dots . .. ... (reset) ...


3

I think the search icon (great icon by the way) can be used to make the user understand that a search is going on pretty much as is. The only changes I would make are: The icon should only be displayed while a search is going on, once the search is over the icon should disappear While the search is going on, the icon should be blinking (optional) The ...


0

The main reason you should separate them is to avoid users accidentally creating new accounts. I tried to be similarly creative with a form like this in the past, and ended up with tons of users who tried to "login" using the registration form, and then wondered why all their data had been deleted. Even though I didn't let existing users register, given ...


0

An accordion as suggested by Boranas is your best bet. Another suggestion would be to add highly visible + and - buttons to the accordion headers to be touch friendly


1

The first problem is that you have only one link "add" for different kind of content. If you can it should be better to contextualize each link : "add a product" on your product list "add a link" on your link list "add an image" wherever you need to insert the picture Then when you ask him to choose a kind of product, he is already answering a question, ...


1

You can simplify it by transforming the tabs into a decision tree. Something like this accordion control : Then you can just pop up the right(single) window, instead of popping up a window with tabs.


0

What is a valid user name? Is it a user name that was sent to the user from the application when he or she signed up? if so, you should indicate it instead of a generic "Please enter a valid username." If the user name is what the user entered when signing up, you should have a link "forgot my user name." Users are forgetful, and instead of making them ...


1

Given the nature of this task I would offer a single text-area where the user can write or paste the emails separated by a space, a semicolon or both. Below the text-area there could be a greyed out sentence that counts the number of available emails allowed. If the number of email addresses exceeds the allowed amount, the text gets red and the sentence ...


1

A set of checkboxes is by nature multi-select. However, No Friends and the other options are mutually exclusive options. I would simply eliminate the No Friends option. If they don't want to share with any friends, they simply leave all checkboxes unselected.


1

The first comment i would make is you could review your selection titles. It seems from your question that 'within 10km exactly' is not inclusive of 5km, this does not make sense. Re-wording to 'Within 5km-10km exactly' would add clarity. - You could look to apply more logical/specific titles to all selections. Another way to better represent what you ...


1

The larger distance radius can't exclude the smaller radius, in my mind. So just a simple toggle button with a slider can simplify this:


0

Like others already said - go with "Search". It's a most common word pattern used in most interfaces since ages.


0

I would highly recommend using the word "Search" as it is the convention most common on internet and desktop applications. In specific instances you may want to break the convention/expectation, but there should be a good reason. (For example, perhaps this is an application for a specific set of users like Librarians and the word "Search" is already strongly ...


4

'Search' is universally associated with the functionality you've described above. When the user comes to the page, the button takes secondary importance as you need the user to do some filtering/ selections first. In this case, you can keep the button greyed out till all required selections have been made. 'Update results' would be a good choice if the ...


0

Every case is a special case when it comes to UI design, so you should always experiment and see how well actual users understand your designs. But the image below should help you get to a first approximation of what might be a good choice. (And also read this article by Jakob Nielsen.)


3

I don't have any "official" or user tested information about this, but in the examples you have detailed in your question, the sentence case works well for answer which are based around a response you would generally hear someone speak. It makes sense that "value" answers would be capitalized. i.e. Express Delivery Economy Delivery


0

For this case, I will suggest you: Use for all three possible functions the same user interface element: Buttons. Reorder your functions. On the top provide two buttons. Stage 1 and Stage 2 The sum of width of the two buttons defines the third button on the bottom for the accumulated functions The result can look like: [Stage 1] [Stage 2] [Stage 1 ...


0

Simply give an option for a user to choose how many questions should be displayed at once. This will give user "Control and Freedom"


1

The best approach is to support both leave the decision as an option to the test writer. Some teachers prefer one over the other. Some teachers also may want to control whether or not the student can navigate to previous questions.



Top 50 recent answers are included