Front end developers: stop moving things that I’m about to click on
261–270 of 365 posts
Re: Front end developers: stop moving things that I’m about to click on
#262Even if you can't find anyone who specifically can be blamed or had a conscious plan, it seems like something that would be an emergent phenomenon.
"Invisible hand" as they say.
Re: Front end developers: stop moving things that I’m about to click on
#263Re: Front end developers: stop moving things that I’m about to click on
#264I 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
Can someone please tell the Windows Start Menu designers? Have completely ruined the experience as it constantly juggles items as its heuristics are seemingly updated. I especially enjoy how Bing results get prioritized over local applications and files.
Yeah, MS is not good at search, but I think having one engineer tackle windows search for over all these years would have brought us instant and relevant search results.
How many times I have to find the right keyword to find something I KNOW is there but that satisfies the search engine is more than I want to recount.
Re: Front end developers: stop moving things that I’m about to click on
#265Earlier quoted context omitted.
But most of all it doesn’t seem to be deterministic. Very often I get a different behavior on the second attempt. Search in windows puzzles me. Like I don’t get why it takes so long to search files in explorer, while traversing the same folder structure programmatically takes milliseconds. Hard computer science problem!
I think search in windows makes a stab at searching content as well, and not just straight text. This means unpacking zips, loading excel files etc. But, yeah, it sucks.
I suspect it has more to do to explorer registering something with the file system to be notified if any of the folders being searched change or something like that. Something completely useless in any case, I'd much rather it doesn't do anything smart and gives me a result instantaneously.
Re: Front end developers: stop moving things that I’m about to click on
#266I noticed it a lot on Google products where it annoys me quite a bit. It does this in search where it expands a bubble thing with irrelevant carousel content just after the first results (cannot even recall what the content is because it is not helpful). That pushes the entire list of results down making me either click the wrong search result or waiting before clicking. Both probably good for OKRs but horrendous user experience.
Worst one is though on (Pixel) Android where it does this in the notification when receiving a call. It starts with bubbles for "decline", and "accept" but then after a second it inserts "screen call" in the middle, replacing "accept". Screen call is a accessibility feature that breaks the expectation how the call works (no voice). It made itself used the first time for when trying to take an important call. A completely unnecessary move, as the list of options could just be appended... This again makes me wait for all options to come up before clicking.
Re: Front end developers: stop moving things that I’m about to click on
#267Earlier quoted context omitted.
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.
Since Office apps started putting an increasing number things in the title-bar (search, autosave, username, filename) there's limited dead space to use for traditional things like dragging and maximise / restore. I'm never sure where to 'grab' or double click - I don't know if I'm going to start a click-failure cascade if I do it in the arbitrarily, non-obviously 'wrong' place.
Re: Front end developers: stop moving things that I’m about to click on
#268Apple maps enrages me for doing this. When you first open the app it like shows a screenshot of what you were looking at last time while it loads. Sometimes that screenshot is retained as the active view (for example if I have a search up), but other times after a couple of seconds the whole app just resets. This causes me to hit the "dictation" button quite often instead of the X button that was on screen when I sta…
> Apple maps enrages me for doing this. When you first open the app it like shows a screenshot of what you were looking at last time while it loads. This has started to really irritate me since it feels like every application in Apple's mobile ecosystem does this. My device has SIX GIGABYTES OF MEMORY[0]. Why do you need to swap everything out of RAM almost instantaneously? What grinds my gears the most is that state…
Re: Front end developers: stop moving things that I’m about to click on
#269Apple does this, a lot. The number of times I have incorrectly called somebody on FaceTime because I clicked on a contact at the same time FaceTime decided to update the list should be embarrassing for them. I have zero idea how this doesn't get fixed. It should be a trivial change to make sure the list is updated however they'd like before showing it to the user. As it is right now, given that it's slower or about a…
Re: Front end developers: stop moving things that I’m about to click on
#270Apple does this, a lot. The number of times I have incorrectly called somebody on FaceTime because I clicked on a contact at the same time FaceTime decided to update the list should be embarrassing for them. I have zero idea how this doesn't get fixed. It should be a trivial change to make sure the list is updated however they'd like before showing it to the user. As it is right now, given that it's slower or about a…