Tag Info

New answers tagged

1

How about this? Group is not redundant and also in line with the options.


-3

I would also suggest you carefully consider the order of the values. Ordering values from 10 to 1 (instead of from 1 to 10) leads users to give an higher average rating (you can find more informations in this answer I wrote a couple of days ago). You may also want to have a look at the primacy effect: a cognitive bias that results in a subject ...


2

Avoid abstracting the label from the control wherever possible. That is, avoid separating the control and the label that describes the control's state because that forces the user to look in two different places in order to understand what's going on. Instead combine them so that the control clearly describes its own state. In this particular situation, I ...


2

I don't think you should base UX on what pleases you. What will most users understand? The way Microsoft does it is what most users will understand. I think a gray check is more intuitive but I went with the way Microsoft does it. I am responsible for an app that is in an industry that is not computer savvy and have these battles with marketing all the ...


1

If we're talking iPhones 40px on a non-retina screen is the same height as 40px on a retina screen. The device doubles the height accordingly as needed on retina to make sure it's physically the same size.


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.


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

Elessar is a library that lets you have one number line with multiple ranges that cannot overlap.


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


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


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

If they are on a mailing list then, get notified helps if there's the interest, however: Thank you for your interest, if you would like, we can register you early for access when the app is ready. Also, Thank's for registering in our newest product, please confirm your email and add us to your allowed list. We'll let you know when we let it shine. To ...


0

Why not answer this question with science: Randomly show visitors one or the other, and see which one gets a higher rate of registration. Since you have a hypothesis that the waiting list concept could be an emotional pull, this could be perfect for an A/B test like this.


0

I would prefer the first one.. "Get notified" etc. This is straight to the point and can easily be understood as "launch will happen soon. join in now" You could also use "Request an invite". For a more exclusive tone "Join the waiting list" may make it appear more attractive, but it also has a slight negative and longer timespan ring to it for some ...


2

The top answer is excellent, but I thought I would share an alternate idea for this. I would love to know if others think this is useable/a good idea, since I don't have any research or data to back this up: A colored bar, either on the right or bottom, like a "progress bar" shows how much relative text has been entered. It is green until some point, then ...


1

Well, if there is a use case, when a user needs to select several items at once for some reason, the second (new) design has a major flaw - there is no easy way to get all the items you want to show at the same time. You need to execute several searches. Otherwise, assuming there is no value in selecting several items at once, other than storing the ...


4

Don't implement bad UX just because it's legacy. Updating several fields on different items and then save all elements in once is a really bad idea. How do you provide feedback to the user that item 1 (fields 1,6,7,8 where saved), item 2 (fields 2,4,5,6) were saved and item 3 (fields 2,3,7 where saved but field 9 has an illegal character) in an all-in-once ...


7

The most effective placeholder text I've seen is on the Polar sign up form. The placeholder text is an explanation of why the field is there or what the requirements for the field are. I can think of a couple reasons for this: Most people already know what a "First Name" is without you giving them an example. We don't expect to see full sentences in ...



Top 50 recent answers are included