| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 6 months |
| seen | Mar 25 at 0:04 | |
| stats | profile views | 11 |
|
Nov 14 |
answered | Fixed Feedback button on the side of LEFT or RIGHT side of the window? |
|
Nov 13 |
awarded | Editor |
|
Nov 13 |
revised |
Where do users expect to see feedback? added 84 characters in body |
|
Nov 13 |
answered | Where do users expect to see feedback? |
|
Nov 13 |
comment |
How to display “Helpful” rate in the result page? I agree with @Igor-G. You can either go with net values like the voting system on this site, or you can do what YouTube does with a ratio of helpful/not-helpful (the bar represents 65% found this helpful without using a full on sentence). The only thing that I would be careful of is the consistency of the language from the article page and the search results page. If you're doing votes, using the up/down metaphor works. If you're going with ratios then helpful/not-helpful buttons or sliders would work. |
|
Nov 13 |
answered | Finding out how users respond to look and feel |
|
Nov 13 |
comment |
Which one has more career opportunities: web usability or web accessibility? Furthermore, design isn't necessarily just visual, and the definition of a disability is so broad in itself. It may be ordering the information (e.g. content before navigation) appropriately so that users with screen readers have a good experience. Or it may be making the font bigger so that our grandparents can read it. So yes, I believe a good designer or usability consultant is definitely mindful of these nuances. |
|
Nov 13 |
comment |
Which one has more career opportunities: web usability or web accessibility? But that's what I'm trying to get at: UX isn't just about design. You may be more well-versed in usability or accessibility, but to put together a great product, you have to understand how these different aspects work together. This is especially true if my client is government-based, or whose majority of the users have a disability where accessibility = usability. |
|
Nov 12 |
comment |
How does having multiple stages of a form affect conversion rate? +1, especially on managing expectations. BJ Fogg's model of behaviour design states a task is perceived simple until it requires a resource (e.g. money, time, cognitive cycles) that the user does not have. If you want to make a task appear simple, set expectations high. Practically, this may be (1) acknowledging a task is hard (don't make the user feel stupid), (2) letting the user know it's easy despite the number of steps (e.g. "2 minutes from..."), or (3) setting the tone with that first page or section of the form (e.g. step 1 is easy => step 2 should be easy as well) via visual design. |
|
Nov 12 |
answered | Which one has more career opportunities: web usability or web accessibility? |
|
Nov 12 |
answered | UI to let user pick some movies (3 - 6) from all movies released till now (>1 M) |
|
Nov 9 |
comment |
Displaying a large data table in a mobile app Mobile as in phone or tablet? Like @Anna mentioned, the client may say all fields are required, but chances are, they aren't. Especially on the phone, the type of operations they can perform comfortably will be limited. |
|
Nov 9 |
answered | Where can I find a comprehensive list of UI Components? |
|
Nov 9 |
answered | Move filter from sidebar to top? |
|
Nov 9 |
answered | Form builder that allows dynamic flow based on answers |
|
Nov 9 |
comment |
How should I determine where to place an application version number? About the styling: "Awesome Application Version 1.0.1" would be harder to process than "Awesome Application, Version 1.0.1", for example. You can easily tell what the important information is versus meta information. |
|
Nov 8 |
awarded | Supporter |
|
Nov 8 |
awarded | Teacher |
|
Nov 8 |
answered | How should I determine where to place an application version number? |