Reputation
28,042
Next tag badge:
91/100 score
28/20 answers
Badges
3 46 84
Newest
 Nice Answer
Impact
~895k people reached

20h
comment Why is the 0 next to 9, not next to 1?
@DavidRicherby possibly. It's just a horrible example all around. It looks like a horrible auto-trace of a bad photocopy of a microfiche scan. :)
20h
comment Why is the 0 next to 9, not next to 1?
@gerrit technically, UX as a field of practice wasn't around in the typewriter era. :) But that said, this likely wasn't UX related at all. A lot of things ended up the way they are not by design as much as by engineering, random opinions, or by accident. There may be a UX tangent here, but it's slim, at best.
2d
comment Why is the 0 next to 9, not next to 1?
@supercat which is fine. I'm not a fan of this question to begin with, and that we really can't answer the question only emphasizes that. We can come up with lots of great theories and guesses, but that's all they are...just theories and guesses--and none are really related to UX Design.
2d
comment Why is the 0 next to 9, not next to 1?
I don't think people number their shopping lists. However, I do like the theory that zeros usually FOLLOW a number, rather than precede it. Though I think that's just a theoretical reason for the placement.
2d
comment Why is the 0 next to 9, not next to 1?
I don't know that there is a strong correlation between a rotary phone dial and a typewriter. There could be, but there's also so many differences that it seems unlikely.
2d
comment Why is the 0 next to 9, not next to 1?
I'm not convinced that that "Sholes and Glidden" example is at all accurate. For one, it's not monospace...which would be very odd for an early typewriter. Possible, but unlikely.
2d
comment Why is the 0 next to 9, not next to 1?
"real answer must lie in history..." Indeed. Alas, that's a history question--not UX.
2d
comment Use of TWO hamburger menus in mobile app
This answer certainly isn't wrong, but I'd take the linked articles with a large grain of salt. Whether a hamburger menu is good or bad is heavily dependent on context. Sometimes it really is a good solution.
2d
comment Use of TWO hamburger menus in mobile app
How would a user have any clue as to which one to tap at any given time? When a client insists on something stupid, if viable, see if you can do some ad-hoc user testing. Sometimes data will change their mind.
2d
comment Suggestions and references for a modern-looking and clean UI?
As for this example, give us a use case. Would a user typically be editing all of these records in one sitting? Or just one or two?
2d
comment Suggestions and references for a modern-looking and clean UI?
These are fine suggestions for a broad page framework but don't really address the specifics of the question.
2d
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.