Reputation
495
Top tag
Next privilege 500 Rep.
Access review queues
Badges
2 7
Newest
 Student
Impact
~16k people reached

  • 0 posts edited
  • 0 helpful flags
  • 21 votes cast
Feb
25
comment Ask user to input UTC timedifference
If it's only for USA use, I'd say break it down to state selection, but that's a rather US-centric approach that I don't think really works elsewhere. The nearby major cities however can effectively work as a stealth method of doing that, assuming that each state has the same time zone everywhere within it's borders. (But I might be wrong)
Feb
18
revised Ask user to input UTC timedifference
Added location awareness suggestion
Feb
17
comment When does a combo box get unwieldy?
What about if the dropdown (which has hundreds of entities) is already for the smallest logical categories for our system? This is for selecting the business entity belonging to a customer; our customers commonly have hundreds of business entities, with no grouping scheme that will make it easier to scan through, and nobody wants to scroll through a combobox with potentially up to a thousand (and theoretically, more) options, but might in some cases have just two.
Feb
17
comment When does a combo box get unwieldy?
It doesn't have to be a 3 column layout. (Our legacy system is actually a single column, and whilst it doesn't doesn't display as a radio button group, it has the behaviour of it)
Feb
17
comment Ask user to input UTC timedifference
In which case, I would go for major cities. Possibly taking advantage of location awareness if the device is capable of it, to narrow it down to the sensible selection (i.e. if the device is aware that it is in North America, there's no point providing a list of cities in Europe or Africa)
Feb
17
answered Ask user to input UTC timedifference
Feb
17
comment When does a combo box get unwieldy?
Are there any studies or research you can think of to support this?
Feb
17
comment When does a combo box get unwieldy?
Sadly no. The list is of the business entities, and our clients are of the "we own hundreds of companies, who may have hundreds of holding companies" variety, and we need to be able to select any one of them. The list of "possibly several hundred" is already the result of sorting and filtering.
Feb
16
awarded  Student
Feb
16
asked When does a combo box get unwieldy?
Feb
4
comment Button for “Play, but from beginning” for a scrubber UX
Many video editors work on a mac, and most macs these days have the smaller keyboard that doesn't have a home button. This of course may not be an important consideration for the software (Windows only environment, user demographics suggest that they have full-size keyboards etc.)
Feb
3
awarded  Critic
Feb
3
comment What are good reasons (if any) for intentionally breaking the affordances of an input field?
Actually that makes a lot of sense in this context. It's been done piecemeal, and it's inconsistent about where this happens, so I guess one dev worked on it in this way and it slipped through the cracks.
Feb
3
comment What are good reasons (if any) for intentionally breaking the affordances of an input field?
To be honest; "That doesn't make sense, and we can't think of a reason either" is a really useful answer. I'm trying to check I didn't miss something obvious.
Feb
3
comment What are good reasons (if any) for intentionally breaking the affordances of an input field?
Precisely. It was just so extensive, that I felt the need to get sanity checks from other UX pros that I wasn't missing something obvious.
Feb
3
awarded  Commentator
Feb
3
comment “We emailed instructions to bork@bork.bork”
The argument could be made that the TLD makes it obvious that it's an invalid email address, but I would caution against that, as you don't know when and if .bork will become available.
Feb
3
comment Copy for a checkbox - Positive or negative?
What if the opt out was an opt-in checkbox that was enabled by default? That would likely have a noticeable impact
Feb
3
asked What are good reasons (if any) for intentionally breaking the affordances of an input field?
Dec
31
revised If the output from a webapp can't be made accessible, is it worth it to make the rest of the webapp accessible?
Fixed a wrong word, and inserted a caveat about it depending on the level of impairment.