Tag Info

Hot answers tagged

21

Try to distinguish between what users want and how they want it done. Taking your example above, users wanting one vs. two input boxes is all about the how. The what is being able to paste comma-separated coordinate pairs vs. not having to press comma. (Or, for some users, being able to simply press comma rather than having to click a second input box.) In ...


15

You can't please everyone Most changes or additions will leave some people behind. They may catch up later, they may hate you forever. Shoot for net gain in the experience. If you avoid negative feedback, you avoid progress. It helps to keep a destination in your sights. Focus on an established list of goals for the long term vision of the product and the ...


8

If the exams option is always empty, then the users will (at some point, depending on the individual person) give up checking that menu option. If there is no mechanism in the application to draw the attention to new exams that appear, then you have a usability issue. Your suggestion is one way to indicate the "new items" idea, but it is not necessarily ...


4

I see several aspects in your proposal that I would solve differently. "Flash cards" appears disabled, but is actually a valid option. That option currently appears as disabled as your "locked" option. I'd color all available options black, not gray, to avoid that. Show clearly which option is currently selected. It's always a challenge to show which one ...


3

Accommodate both! In this case, your users told you exactly what they were missing in the old version (in this example, easy copy/paste). So create a new way that meets both sets of requirements. Generally speaking, say the old way offered Features A and B, and the new way still supported Feature B, lost feature A, but added feature C. Users said they ...


2

I know this could be off the chart but just want to share this


2

If you have feature requests, complaints or questions on your forum or even public places (StackExchange, Quora etc) from your users asking for solutions to problems that normally should already be solved by the implemented features, then you need to rework that part. If you have very low usage with no requests then it is safe to assume is not something ...


1

I think it depends on the type of feature you want to show / hide Incase you are working on a consumer / creative app like say a presentation software or a cartoon maker or a video editor etc. (please excuse the silly examples) In these, the user can choose items / effects / characters / tools etc. In this case, you can easily grey out the PRO elements from ...


1

I would say that: show it at the first place but disable (disabled button/text) Is the right approach as it gives users an idea about how their "expertise" rewards them as well as an idea about what they need to to do in order to achieve progress towards a desired set of goals. the review feature in UX.SE offers a good example of progressive ...


1

I agree that directing to different pages based on the state is confusing. Also, it will be annoying if the user just wants to perform some other task and is interrupted by the connection request. It would be better just to highlight the connection requests more. You could, for example, put a prominent notification near the top of the site, which persists ...


1

A user typically chooses to filter by brand because they want to see products from that brand, regardless of how many products there are. Listing the brands in alphabetical order is therefore sensible because it makes it easier to find the desired brand in the list, compared to presenting them in a random order. It is still useful to know how many products ...


1

Example: user's real-life name has changed. In many systems, a username is based on the user's proper name, e.g. given name initial plus family name "jsmith"; over time, these users may change their names, and wish their system username to change to match. One particularly sensitive example is if a person divorces, and reverts from their married name to ...


1

One book I'm going through now is Interactive Design by Andy Pratt & Jason Nunes. It focuses on UX in general, but introduces you to UX practices and methods through real-life examples, which in turn gets you thinking about how to consider it in your own application. It covers some design principles, such as Affordance" and gives concrete examples of ...


1

FavBrowser as very good ones for the specific case of Internet Explorer 6: Why People are Still Using Internet Explorer 6? You Seem to Be Using IE6 Internet Explorer 6 Motivation How To Deal With People That Use Internet Explorer 6 Internet Explorer 6 CSS Mess


1

I personally don't like the idea of graceful degradation, especially now that almost every new Windows PC from an OEM ships with Chrome preinstalled and Mac's should mostly have some sort of version of Safari that supports most HTML5 features. One approach is that the app is either fully supported or it doesn't work and the user is pointed to a free web ...


1

You use the data to answer questions. So: If you know the questions you are asking, gather the data you need to answer your questions. If you don't yet know the questions you are asking, gather everything (or as much as possible and practical).


1

Does it matter how many users use a certain feature for it to be implemented? Off course it is, but as Stephen has said, this is much more of a product management business than UX (particularly as you talk about implementation), but UXers may be the ones deciding priorities as well. Coding We do quite some coding in UX. Perhaps the most obvious place ...


1

Shortcut keys are the domain of more experienced users who know the system and like to get things done as fast as possible. Your problem as I see it boils down to "How do I help a user get from beginner to advanced?" The problem is that people don't look for new features and new ways of doing things, they just stagnate. Whatever the underlying biology, ...


1

You can use a check box type thing to mark the data block, and single click to move the user to block details.



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