Live data from Hacker News

Front end developers: stop moving things that I’m about to click on

medium.com

71–80 of 365 posts

Re: Front end developers: stop moving things that I’m about to click on

#71
Something that really frustrates me is when an alert pops up on my screen just as I'm about to tap something, so my tapping then dismisses the alert before I've had a chance to read what it said.

Hopefully the contents of said alert weren't important, but in most cases I'll never know…

Re: Front end developers: stop moving things that I’m about to click on

#73
Google with its 'related searches' that pops up because I clicked on a link and I am almost never interested in this extra information. When trying to filter the relevant javascript it breaks some other stuff on the page (last time I tried a few years ago). Grrmbl

Re: Front end developers: stop moving things that I’m about to click on

#74
Instagram search is my daily frustration. 100% of the time I search I’m looking for a user’s account. Type type type, see the user come up in results, go to tap but now they’ve loaded in 10 possible autocomplete options for my search, pushing the thing I want off the screen. And of course now I’m in the “explore” page with a search term I don’t want, taking a bunch more taps to get where I need to go.

I agree with others that I think the incentives are against the user here. In the IG case they don’t care if I find my friend quickly. It does not help them in any way. But hey they got a click on the autocomplete suggestions (win for that PM) AND another view on the explore page. Clearly I love these features!

Re: Front end developers: stop moving things that I’m about to click on

#77
post #68
post #15

A particular bane of mine is the self-oscillating UIs, youtube is particularly bad at it these days - if the mouse pointer is in 'just the right place' (which is bigger than it sounds) then you get the seek-bar preview frames popup, which moves things just enough that the mouse pointer is no longer over the area that triggers it, so it vanishes, and the whole thing starts again.

YouTube also has the problem that there is almost no dead space to "park" your cursor. You have to carefully place it in between autoplaying previews.

I've noticed this with JIRA, there is not much space to click 'safely' to focus on the window

Re: Front end developers: stop moving things that I’m about to click on

#78
post #28

Oh, it gets better. On Android (at least, LG-flavored one — never used any other android phone) I have an issue with inter-app "Share" button popup. It somehow manages to re-shuffle all the suggestions (apps/recipients) exactly in the same amount of time that is natural for me to spend before clicking on the desired contact. Which several times made me send something to a wrong person, which resulted in extremely awk…

I'm on Samsung and it doesn't re-shuffle as you're looking at it, but it's in a different order every time. It's so irritating if you're doing the same operation many times, ie sending the same picture to multiple people separately. Also the share menu has a different layout according to what app you're using. I understand that it's up to the app developer to get fancy with it, but it would be really nice if you coul…

Same here, every time I share something from YouTube --> NewPipe, the icon is in a different place, even when I'm adding multiple videos to my queue one after another. Every. Damn. Time. So frustrating.

Re: Front end developers: stop moving things that I’m about to click on

#79
post #7

I agree with [this][1] idea: > an autocomplete has one chance to reorder per keystroke. if you got it wrong and you have a better ordering a bit later you must “swallow the sadness” (as per the original author of this wisdom) but never change already displayed items [1]: https://twitter.com/dan_abramov/status/1470751551568363530

I want foo.

- Type 'f'

- foo appears in the search.

- Type 'o', because I type with 10 appendages and getting them to work together requires pipelining.

- foo disappears from the search

This should never happen.

Re: Front end developers: stop moving things that I’m about to click on

#80
This problem first occurred in the mid-'90s, and people saw it was a problem, and that's why we specified the image dimensions in HTML (before the GIF or JPEG header was loaded), so the layout wouldn't shift during load, when people were already reading and navigating.

Since almost the beginning, graphic designers were trying to layout Web pages like an advertising brochure, lots of bad ways, rather than as hypertext. When, in a sense, they finally did take control of the Web, HCI (usability in service of user) had evolved into "UX" (advertising-like graphic design in service of non-users).

There's often disincentive for things like "user can understand what the controls are and what the state is", "user can focus on the information they want", etc. UX won't care about these things until some time after users are so aware of the problems that it affects engagement metrics and eventually A/B testing figures out why.

I'm imagining a eureka moment, during which a UX researcher, trying to find a new, improved dark pattern, to screw over hapless users harder, accidentally lets slip in some old-school good usability, which wasn't even supposed to be in the test sets, but discovers that this strangely resonates with users.

Post reply on HN