Tag Info

New answers tagged

0

Without understanding your situation thoroughly, I do have a few suggestions you might consider. Consider an interaction similar to "Snackbars and Toasts" from the Google Material Design UI and stack them as needed. Consult that handling of GROWL notifications for Mac users and how they stack notifications - especially if you'll have many notifications ...


0

I am programmer learning a bit of UX so I may get beat up by UX purest but I capture metrics on user productivity. If a top performing user asks for a tweak I will take that over a low performing user. I am in an environment where contract data entry use more than one product. Too often a low performing user will state the (my) product is the problem. I ...


0

User Experience isn't about taking exclusive decisions, is about make the overall experience for the majority of users, the best as possible. I will use your use case as an example. Previous version Single text field, coordinates separated by comma. Advantages: copy/paste is smooth Disadvantages: readability New version Two text fields, one per ...


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


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


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


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



Top 50 recent answers are included