Reputation
28,168
Next tag badge:
100/100 score
20/20 answers
Badges
3 46 86
Newest
 Nice Answer
Impact
~905k people reached

Apr
17
comment Suggestions and references for a modern-looking and clean UI?
Sometimes a "straight excel sheet" UI is the ideal solution. Not saying it is your case, but don't discount it outright. If you've used the web app Toggl, I think that's a great example of overthinking what is, essentially, a spreadsheet and would have been better presented as a simple spreadsheet.
Apr
16
comment How to convey: “don't move until the task is done!”
@KitGrose true. Point is there's a delay that probably shouldn't be there in the first place is UX is the focus.
Apr
16
comment Is address line 1 + address line 2 an anti-pattern?
@Crissov Interesting! please elaborate!
Apr
16
comment How to convey: “don't move until the task is done!”
I don't mind this question as much as many of the other physical device centric questions that get asked here, but keep in mind that this is a very narrow question in that it doesn't have a whole lot of relevance to anyone else not having to deal with this one particular poorly implemented technology. I'm wary of questions that are essentially "I know this is bad, how can we apply a band aid to it" as I don't think that should be what UX focuses on. My 2 cents.
Apr
16
comment How to convey: “don't move until the task is done!”
@LS97 I don't entirely disagree, but do be wary. I often run into the situation where technology failures are blamed on UX due to bad design, mainly because the powers-that-be didn't realize that proper UX requires that good technology be used from the start. And while I love 'fixing' things, I also find that UX bandaids can actually hinder a proper solution as it can tend to mask the real problem that should be emphasized as the source of the pain point and fixed sooner than later. Point being, UX is the technology. If the technology is bad, UX is set up to fail from the get-go.
Apr
16
comment Is address line 1 + address line 2 an anti-pattern?
(I am, of course, way over thinking this. Not trying to make an argument! I just find it an interesting topic I had never thought about before...)
Apr
16
comment Is address line 1 + address line 2 an anti-pattern?
@plainclothes that's an interesting requirement though. Because the post office wants it a certain way, we're asking you, the user, to accommodate. Not that that is an invalid reason, but typically we don't like forcing users to do the formatting required by 3rd parties. I'm also not convinced the postal system needs 1 2 or 3 lines. As this is a form, odds are it will be mechanically printed on the label and OCR will pick it up. Whether it's one line or two lines seems like an antiquated issue these days.
Apr
16
comment Is it a good idea to require users give an email address to see our prices?
No, it's not a good strategy as out of the gate it breeds distrust in the relationship. It makes your company feel like a used car salesman who makes prices up on the spot.
Apr
16
comment Is address line 1 + address line 2 an anti-pattern?
@plainclothes I don't entirely disagree, but I'm not entirely convinced, either. Look at the article Poyi links too. I think my main hang-up is that we're essentially separating an arbitrary data field into two arbitrary data fields. Granted, addresses are arbitrary, but I'm not convinced two fields is making that easier to input for the user.
Apr
15
comment Is address line 1 + address line 2 an anti-pattern?
Do those officially have to be two lines, or is that merely how they are printed?
Apr
15
comment Is address line 1 + address line 2 an anti-pattern?
Right, but neither of those seem UX-friendly. There's no reason (that I can see) that an address can't be on one line vs. 2. The article that Poyi links to above is actually pretty good...it talks about how it adds confusion more than helps.
Apr
15
comment Is address line 1 + address line 2 an anti-pattern?
Why is it mandatory?
Apr
15
comment Is address line 1 + address line 2 an anti-pattern?
@Poyi that's a really good link! Great info!
Apr
15
comment Should I make an effort to prevent trivia questions from being repeated too quickly?
I think the answer to this is simply "yes".
Apr
14
comment Form validation and disabled buttons
Buttons should never be disabled. It's an anti-pattern.
Apr
13
comment Optimal duration for animating transitions
My rule of thumb: make it as fast as you think looks good. Then make it slightly faster (my theory is that we're enamored by our own transitions and the actual users will be more enamored by the sense of speed with them slightly faster).
Apr
13
comment Why is it important to focus on user needs as opposed to requests?
Apple took the approach to not even bother asking what people wanted as they knew that wasn't going to lead to the best solution. "A lot of times, people don't know what they want until you show it to them." - Steve Jobs
Apr
13
comment Should a conversion to a responsive layout happen site-wide at once, or is incrementally acceptable?
I re-worded your question to make it UX-centric. I don't think using bootstrap is really germane to the question. Let me know if I missed the mark on the edit. FWIW, I have this exact same question as we're about to do the same (gradual roll-out of a responsive site) which definitely seems less than idea. Would love any data anyone has on the pros and cons of an incremental roll out.
Apr
13
comment Partial-Page Responsiveness, or Responsive Elements in a Non-Responsive App
We're in the same boat. I have to agree with you, making something 'half responsive' defeats the entire purpose of being responsive in the first place.
Apr
12
comment Web version of a complex business form
Also, bootstrap wouldn't be an appropriate CSS framework for this. The point of bootstrap is to make a responsive layout. The point of complex printed forms is that they are in a fixed canvas. You could use it, of course, but likely overkill as you wouldn't be able to leverage much in the way of the responsive layout features.