Main Page Related Sites RSS Feed
There's been an infuriating trend in software UI/UX for the past several years that's been driving me insane-- Developers that think that they know what I want better than I do.
Probably the best example of this is "autocorrect". The name is misleading-- The end result is almost never correct. I could count on one hand the number of times autocorrect in Google search was actually helpful, and every other time, it was asininely wrong. The result had nothing whatsoever to do with what I was trying to search for. I stopped using Google in favor of Duckduckgo, not because of Google's privacy issues, but because Google's autocorrect was so aggressive that I rarely had a search work correctly. Duckduckgo also has an autocorrect, but it's not quite as bad as Google's.
And don't use autocorrect when texting. "See you at ninw", makes sense. I can tell you were trying to write "nine". "See you at chipmunk" does not give any useful information.
Another example is inline autocomplete. Autocomplete where it would display options that I could choose would be much better, but still not necessary and mildly annoying. Inline autocomplete, though, is something that I cannot tolerate. I used Firefox over Chrome for years because Chrome's self-important lead engineer refuses to allow users to disable it. Recently Firefox for Android has followed suit, so I'm actually going to try to compile Firefox myself with it disabled. I don't know how successful I'll be, but inline autocomplete is so infuriating that I don't feel like I have any other choice.
The incident that prompted this particular rant was Discord's search function. I tried to search for one particular Discord for "confessing baptist", including the quotes, because I wanted an exact search. It completely ignored the quotes, so every separate instance of the words "confessing" and "baptist" were included in the results. It also assumed that I wanted all variations of "confessing", so it included "confession". The final search results were meaningless. I was trying to search for a particular phrase, and it was just not possible. I wasn't able to do the search that I needed, though from a technical perspective it would be insanely easy.
Software's behavior should never be unpredictable. Just do what I tell you to do. If "autocorrect" changes or adds to what I type, if it means that what I tell my computer to do is not what it does, then it's not a feature-- It's a bug. Or, more accurately, it's an antifeature.
An antifeature is a little more than just a bad feature. A bad feature can be disabled-- There's going to be some option somewhere in the menus to disable it. An antifeature is more like an active opposite of a feature-- It actively makes the program worse to use.