Earlier quoted context omitted.
There are two cases where deselecting a floor would complicate the logic: 1. When the currently targeted floor is deselected and the remaining selected floors are all in the other direction: Then the elevator would have to either reverse course without stopping — a situation which otherwise doesn’t occur and would be unexpected and possibly dangerous for the passengers — or stop on a non-selected floor before changin…
I didn't think elevators permitted scenario 1 to occur at all; I thought they refused to allow selecting floors not in the direction of travel. (I don't usually board elevators traveling in the wrong direction, ofc., so, I'm not that sure.)
Where to wait for an elevator (2010)
51–60 of 115 posts
Re: Where to wait for an elevator (2010)
#52Earlier quoted context omitted.
Not worth complicating the UX to address such a minor issue.
Minor to you... Introducing a great experience is the job of good UX. Not simply limiting options and saying 'done'. I am sure there are better options to handle this. Seems like no-one has put the effort into it (yet).
But yeah, I'm sure that at all of the various elevator companies, over all of the years that elevators have had electronic controls, nobody has bothered to put any thought into this.
Re: Where to wait for an elevator (2010)
#53Earlier quoted context omitted.
There are two cases where deselecting a floor would complicate the logic: 1. When the currently targeted floor is deselected and the remaining selected floors are all in the other direction: Then the elevator would have to either reverse course without stopping — a situation which otherwise doesn’t occur and would be unexpected and possibly dangerous for the passengers — or stop on a non-selected floor before changin…
Rather than testing these scenarios, couldn't one simply just(tm) not allow deselection in these scenarios?
Re: Where to wait for an elevator (2010)
#54Earlier quoted context omitted.
I imagine that's by design. Otherwise you could unselect other people's choices.
Yes of course it’s by design. I just wonder why.
[1] https://www.amazon.com/Qualityland-Visit-Tomorrow-Marc-Uwe-K...
Re: Where to wait for an elevator (2010)
#55It seems like whatever minimizes a squared error should itself have some squares in it.
Re: Where to wait for an elevator (2010)
#56Earlier quoted context omitted.
Because in a busy environment (where consistently more than one person uses the elevator) the scenario of making a wrong decision and having the wish to correct it occurs far less than the scenario where someone does not pay attention to which floors have been selected already and deselects your destination. At the worst case this means that you both miss your stop because you both did not notice.
Might also get confusing if the LED indicating the button's been pressed stops working
Re: Where to wait for an elevator (2010)
#57Might be a bit off-topic… But: The one big question I have with elevator UX is this: why isn’t it possible to deselect a choice? So pressed 10th floor but wanted 11th. There is no way to press button 10 and then button 11 to correct that mistake. Will I ever solve this mystery?
Admittedly, that's not very helpful unless you somehow knew that the elevator you were in had been configured in such a way.
Re: Where to wait for an elevator (2010)
#58Is there any intuitive explanation for why the mean minimizes the squared error? I know it IS true - this property is used for linear regressions etc - but I couldn’t actually explain it. It seems like whatever minimizes a squared error should itself have some squares in it.
Re: Where to wait for an elevator (2010)
#59Might be a bit off-topic… But: The one big question I have with elevator UX is this: why isn’t it possible to deselect a choice? So pressed 10th floor but wanted 11th. There is no way to press button 10 and then button 11 to correct that mistake. Will I ever solve this mystery?
Re: Where to wait for an elevator (2010)
#60Earlier quoted context omitted.
Rather than testing these scenarios, couldn't one simply just(tm) not allow deselection in these scenarios?
Then you’d have to test that . And it would still be confusing to users that deselecting only sometimes works.
HN is not representative of the average person, or even a standard cross section of society. A elevator has to be legible to an 8 year old child, an 80 year old retiree, someone who is blind, a person who is deaf, etc.
When designing for such a broad audience, KISS (keep it simple, stupid)