Tag Info

Hot answers tagged

11

Proper feedback is one of the most important parts of creating good, intuitive UX. Leaving it be would provide very little feedback and may cause confusion among your users. From my experience in UX testing, the majority of users don't retain the information presented on many "one time" notifications, so its likely that this won't be the most successful ...


4

Usability shouldn't be looked at in terms of 'will it be acceptable to do x', if you know doing something is bad and you're looking for excuses to do it then you really shouldn't be doing it. Usability should be approached in terms of 'what advantages does doing x have?'. Disabling the back button...what does it give you? I am struggling to think of any ...


2

Nice Design :) Coming to how you can show the content, I would recommend a combination of both using a loading animation to inform users that the new bid is being fetched. So it might look something like this Pulling in new bid from the server This informs the user that a load is taking place. Once the latest bid has been loaded, you could change the ...


2

The usability of a normal select field is greatly reduced for any list involving 5 items or more (yes - 5, not 5k). These components are as old as the web and were never designed with usability in mind. However, they are great when you want to put strict constraints on the input (like when users choose a month for the expiry field of a credit card in a ...


2

You can't directly select an item from such a large list. Lots of information always confuses, so we need to give user a clear path to completion. There are at least two ways to deal with it: Some kind of smart search, or "advanced search" with different options. It would be also good to show information in process about how much items matches your ...


2

The positioning of the back button isn't very good in either of the screenshots. They go easily unregistered since they're out of place and very small, risk making the user frustrated since she won't know how to navigate properly. The third screenshot shows the back button ordered in the same group as Delete and New, buttons for manipulating the content. ...


2

Try re-phasing your question this way... As a user, what are they trying to do? Are they trying to create a new item? Or are they trying to view a new item form? Even though they are technically going to a new page, the end goal they want is to create that new item. The form page is just a sub-step required by your app. To label a link along the lines of ...


2

In the case of bidding, history is relevant. I would add a ticker div on the page. Initially the ticker is hidden. When a new bid comes in, the ticker pops out a little with a message "New bids have arrived". The user can expand the ticker to show exactly what the bid change was ("+$105 on Wuesthof Knives"). As new bids come in, the ticker pushes them ...


1

Buttons initiate a process: Submit, Cancel, Save, etc. Submit buttons can be used by the keyboard to interact with a server, mapped to the Enter/Return key. Links are anchors that connect one HTML document to another. This is a subtle but important distinction. If hitting the button does not save (Post) a current new item (like Save & Continue) then I ...


1

I agree with nightning's answer, but also think that it doesn't really get the point across. The question shouldn't be link vs button, especially for a web-app. The principles behind both are slightly different but often the same these days. A link is as it sounds, a door to a different page. A button is more like an elevator button...you'll get to the next ...


1

I'm always against asking things double, which -in my opinion- provides a bad UX. I would go with option 2 since it costs the user less clicks. It could also be confusing for people that don't understand why you need permission from the browser: They clicked yes on your website and need to click yes again on the browser, that doesn't make sense to them I ...


1

Don't show irrelevant form controls that clutter your UI. Luke W has a good video up on YouTube titled "How to Make Form Input Faster" -- he talks about mobile, but the concepts do translate to desktop. In a Date & Time widget that I recently defined, I wanted to make it more compact and wanted to hide less used information. In my case, must users ...


1

I think the bottom left would be a fine place for it, without being too much work to change. It is better than the bottom center, because it would be the same on all screens. Also, adding the word "back" next to the arrow would help. I don't think it is highlighted enough without this.


1

Designing in an enterprise setting, we frequently distinguish between "Administrators" and "Business Users", the latter meaning users who do not change system settings, but rather pursue business goals with the help of the system. Needless to say, Administrators are Users as well, and usually we talk not of Business Users (because the category often is too ...



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