←back to thread

Are we stuck with the same Desktop UX forever? [video]

(www.youtube.com)
179 points joelkesler | 3 comments | 13 Dec 25 18:39 UTC | HN request time: 0.633s | source
Show context
jhhh ◴[13 Dec 25 22:41 UTC] No.46258932[source]▶
I understand the desire to want to fix user pain points. There are plenty to choose from. I think the problem is that most of the UI changes don't seem to fix any particular issue I have. They are just different, and when some changes do create even more problems there's never any configuration to disable them. You're trying to create a perfect, coherent system for everyone absent the ability to configure it to our liking. He even mentioned how unpopular making things configurable is in the UI community.

A perfect pain point example was mentioned in the video: Text selection on mobile is trash. But each app seems to have different solutions, even from the same developer. Google Messages doesn't allow any text selection of content below an entire message. Some other apps have opted in to a 'smart' text select which when you select text will guess and randomly group select adjacent words. And lastly, some apps will only ever select a single word when you double tap which seemed to be the standard on mobile for a long time. All of this is inconsistent and often I'll want to do something like look up a word and realize oh I can't select the word at all (G message), or the system 'smartly' selected 4 words instead, or that it did what I want and actually just picked one word. Each application designer decided they wanted to make their own change and made the whole system fragmented and worse overall.

replies(5): >>46259329 #>>46259454 #>>46260143 #>>46261226 #>>46262023 #
porkbrain ◴[13 Dec 25 23:38 UTC] No.46259329[source]▶
Text selection used to be frustrating on mobile for me too until Google fixed it with OCR. I get to just hold a button briefly and then can immediately select an area of the screen to scan text from, with a consistent UX. Like a screenshot but for text.
replies(4): >>46259474 #>>46259547 #>>46260467 #>>46261124 #
1. clearleaf ◴[14 Dec 25 03:11 UTC] No.46260467[source]▶
This is such an indictment of modern technology. No offense is meant to you for doing what works for you, but it is buck wild that this is the "fix" they've come up with. As somebody learning about this for the first time it sounds equivalent to a world where screenshotting became really hard so people started taking photos of their screen so they could screenshot the photo. How could such a fundamental aspect of using a computer become so ridiculous? It's like satire.
replies(1): >>46261978 #
2. porkbrain ◴[14 Dec 25 09:56 UTC] No.46261978[source]▶
Unfortunately, some apps don't support text selection and on some websites the text selection is unpredictable.

I'd actually compare screen OCR to screenshots. Instead of every app and every website implementing their own screenshot functionality, the system provides one for you.

Same goes for text selection. Instead of every context having to agree on tagging the text and directions, your phone has a quick way of letting you scan the screen for text.

To be fair, I still use the "hold the text to select it" approach when I want to continue with the "select all" action and have some confidence that is going to do what I want.

replies(1): >>46263731 #
3. zbentley ◴[14 Dec 25 15:30 UTC] No.46263731[source]▶
> some apps don't support text selection and on some websites the text selection is unpredictable.

That correctly identifies the problem. Now why is that, and how can we fix it?

It seems fixable; native GUI apps have COM bindings that can fairly reliably produce the text present in certain controls in the vast majority of cases. Web apps (and "desktop" apps that are actually web apps) have accessibility attributes and at least nominally the notion of separating document data from presentation. Now why do so few applications support text extraction via those channels? If the answer is "it's hard/easier not to", how can we make the right way easier than the wrong way?