Tag Info

Hot answers tagged

29

what to show to the user. Should this also be hidden from the user? You show the user what is actionable for them. For example, if you have an error which is caused because of some null pointer exception and more of a bug than user error you don't want full explanation because they can't do anything different. Or should we show this anyway? Or ...


25

Right now I am browsing this website through my company's VPN which gives me an English IP. While I am in fact a native Hungarian, working physically from Hungary. Is this a good enough example? ;-)


21

Imagine this. I post a status update: I finally finished our renovations! Your comment is: Great stuff! Congrats! I want to do that too. And then I changed my original post: I just kicked old lady. Would you still stand by your comment? :)


17

It is better to explain what the customer will get if you follow their requirements as they are written, and suggest that the requirements be rewritten to clarify the customer's true intent. But generally speaking it is the Project Manager's job to interpret the requirements in a way that will adequately fulfill the customer's needs. It is pointless to ...


15

A common reason for this "feature" is that a site tries to keep some state of the current session on the server side. That desire to track "conversation" state on the server side often comes from trying to write a Desktop-like "rich client" on the web (as opposed to embracing the web as the chaos it is). To be fair, this mostly happened in a time when the ...


14

You should stop coding right now. I'm very serious. If this site is to receive anything more than very simple "design love" such as colors or font sizes, any designer worth hiring is going to want to adjust not just the design, but first and foremost the usability. Great (or even good) user experiences is about more than matching colors and pretty pixels, ...


14

Several reasons: The person using the browser may not speak the language that the browser uses. (Say, someone who is French on an English machine...) The location/language information may not be accurate (for any number of reasons: VPN, proxy, etc.) You could call it laziness on the part of the developer(s), EXCEPT that it is always best not to ASSUME, and ...


14

They have released a UI framework that supports ribbons -- it's just supported in MFC instead of .NET. There's probably room for quite a bit of debate as to why they did things that way, but it is what they did anyway. It looks like Metro-style apps will be supported much more universally -- not only C++, but also C#, VB, and Javascript are supported, if ...


13

The sites that do are really really annoying! Google who are pretty much the state of the art as far as Web UI is concerned get this consistently wrong as far as I (and many other people) are concerned. I travel a lot and it really annoys that I need three clicks to get to "google.com" Intial www.google.com which redirects to www.google.co.?? with all ...


13

I'd say neither. Provide a form where they can report some feedback. Behind the scenes, this form can send you an email, create a github issue, or whatever you want it to do. You can also provide the github link - an asterisk at the end of the page if the users want more information about the current status of the issues. I don't think providing an email ...


12

Take it iteratively. You're working directly with the users, right? So it should never really be a mess. First do the search page. You and the users should keep in mind that they'll want to be able to do actions on the results. Do the users like it? OK, you've got your search. Now add the "Change Password" (or whatever is next in priority). Oops, we ...


11

This discussion always comes up due to one largely ignored fact: OpenID was never designed as login protocol. That's a later misattribution. OpenID was conceived as homepage URL verification service. And for that it was workable. But due to lack of alternatives it was quickly repurposed as general login protocol. Some features were crafted on (simple reg, ...


11

The best solution in this case (and it is mentioned in the question) is simply to remove, or even better, to disable the UI elements that lead to "Access denied" actions. This way, the user will know that they can't do this action. Additionally, some hints can be displayed on these elements that to explain: "Disabled, because this action requires more ...


10

Animations can be an extremely important part of the user interface. They communicate or hint at things a user can do, guide the user through the application or help build up a well defined mental model of the application inside the user's head. Consider the classic iPod interface, where screens slid from side to side to signify the navigation through a ...


10

Is this request technically viable? No, not least because technical users will be able to spoof the requests - that said those users that are capable or walking round the limitations are more likely to be using a browser that doesn't cause you problems. Is this request reasonable? Maybe - but I refer to my earlier answer, the users that can easily ...


10

It depends on who the user is, and what they can do with the information. Generally, try to show them only useful information about things they can resolve themselves. A 40 line stack trace with a regular expression error at the top is not very useful. Much better would be a message that says Date must be formatted as "yyyy-mm-dd". Anything else, and the ...


9

Users tend to stick with 1 or 2 passwords. If the app was hacked by another app, then having the user's password from your service might grant access to other more sensitive resources besides your food service. A better method may be to store some sort of long term authentication token on the phone than the password itself. That token could be tied to the ...


9

I would not force an update on a user. First, it tends to happen that someone's "work flow" or "process" becomes dependent on certain behavior of your app. If you change that, it will cause chaos and anarchy and whining to someone's boss that those mean IT people are stopping me from doing work and they need to fix it NOW. Secondly, like you said, ...


9

Never trim whitespace arbitrarily in an API. The only reason to ever trim whitespace arbitrarily is as a UI feature. People frequently leave spaces at the end of entered fields but can't see that they've done so. It's pretty confusing to return a message, so -- except in the rare case where a user might enter "A " to mean something other than "A" -- you can ...


8

You're lucky. I often have to deal with self-called designers who don't understand basic design neither. by mean they dont understand UX rules and other things like how user interact with the software In other words, they are designers, not software designers or web designers. So they are not suited for their job. This means that you have three ways to ...


8

From user point of view, I would want to know whether whatever I am doing at given moment is going to fail as soon as possible. Which is why I suggest going for key-up validation. Few reasons for it: gives user nice real-time interaction and security feel (system is watching whether you do what you're supposed to correctly) helps user to focus at one task ...


8

Checked exceptions are a failed expriment in language design. They force you to have extremely leaky abstractions and dirty code. They should be avoided as much as possible. As for your points: 1) Checked exceptions make the code dirty, and no less unpredictable because they show up everywhere. 2) How is a checked exception being shown to the user any ...


8

I feel like I say this a lot. Agile does not mean you need to put blinders on to ignore the future and design yourselves into a corner. Agile is about how you deliver functionality, and has very little to do with how you design functionality. In other words, it's okay to look as far into the future as you want when creating your design, as long as it ...


7

Agency (as you define it: being able to control your data in the way that you want to) is in direct conflict with another key goal of user experiences: Integrity With social media it is historical integrity. Another goal that can be thwarted by "more agency" is operational integrity. Historical Integrity — This is Facebook, Twitter, even ...


7

You could use an application to draw mockups instead of writing code. Like Balsamiq Mockups or equivalent. Using Mockups feels like drawing, but because it’s digital, you can tweak and rearrange easily. Teams can come up with a design and iterate over it in real-time in the course of a meeting.


7

If the money values displayed are indeed dollar amounts, you should keep the $ displayed. Not doing so makes the value ambiguous to those not in the US - they might think these are in their local currency. If the values are indeed in local currency (whatever it may be), you should display the corresponding currency symbol (again to avoid ambiguity).


7

The best way would be to provide both. The more way the user can send you feedback, the more feedback you'll get. As was said in a comment, most people won't know what git-hub is or how it works. Nothing prevent you to copy-past the mail received into github to keep a track of the issues.


7

I don't see a problem to set a single supported browser for small intranet applications, if using that browser is within company policy. Ironing out all the little problems with all browsers will likely cost more than an intranet application is worth.


7

That is unfortunate the UI guys don't care about the detail of the complex backend work. This sounds more like a discussion topic for a retrospective. Splitting the team along discipline would set a dangerous precedent, how soon would it be before the Requirements folks begin zoning out and not caring about what the UI guys are doing and ask for their own ...



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