Live data from Hacker News

Stop Using ‘Drop-Down’

adrianroselli.com

1–10 of 19 posts

Re: Stop Using ‘Drop-Down’

#6
Does anyone else see a trend in recent times of posts that start with “Its time to start X/ Stop using X” instead of saying “I think there is some work to be done about X” or “IMO Y is better than X”.

Then turns out you read the thing and they have nothing to sustain that title.

Re: Stop Using ‘Drop-Down’

#7
`Drop-down` is imprecise, especially considering the difference between a navigation menu that drops down, compared with a a list of pre-set options.

There might be a few too many examples on this page, though.

Re: Stop Using ‘Drop-Down’

#8
This is nuts. Please don't encourage people to stop using such a tried-and-tested, well understood, descriptive word. Talking about UI/UX is hard enough without taking that away. What the author is actually criticizing is a lack of detail regarding UX and implementation in feature descriptions.

Re: Stop Using ‘Drop-Down’

#9
Thing is my customer, Bob From Marketing, wants a new feature. He knows "Text Input","Drop Down","Form","Button", "Checkbox" as terms to communicate his feature to me. He knows this because he used to code some Visual Basic on the side when he was "still a programmer" all those years ago.

Now in reality, I don't take any thing Bob tells me literally as directions. I treat it more as a description of Bobs problem. I then forget everything he told me he wanted and build the tool necessary to do the job he's described.

"drop-down" works just fine thank you. It's adequately descriptive to support its most common application - which is communicating with non-technical people.

But what about communicating with a technical person? Well, they're going to do what they want to/the sensible thing anyhow no matter what I call it.

Post reply on HN