Live data from Hacker News

Why Google's bookmark manager and Docs have purposefully bad UI

bookmarkos.com

131–137 of 137 posts

Re: Why Google's bookmark manager and Docs have purposefully bad UI

#131

Flip side - Google Keep. To search for a note you have to press the search box twice . First time you just get types of things - if you want to search free text you have to press again. I'd argue that UI encourages using tags over search. It's honestly my only major annoyance about Google Keep.

Mine is the mix up and slow transition from "Reminders" to "Tasks". And how my assistant can't create tasks in my Google Calendar. Drives me nuts.

Re: Why Google's bookmark manager and Docs have purposefully bad UI

#132

Earlier quoted context omitted.

There is tons if options to find files on macOS: the find command, spotlight, search in the finder, hierarchical view in the finder. Which popular OS has a better system than that?

The search on MacOS is unusable for me. It always surfaces wrong/irrelevant things and defaults to searching in the oddest places.

Yep, Spotlight is my go-to to launch apps but for files, it's either extremely slow, or extremely inaccurate, or simply doesn't show anything but web results. Frustrating...

Same for Finder's search, defaults to searching weird folders and bad at reducing the noise.

Re: Why Google's bookmark manager and Docs have purposefully bad UI

#133
post #22

Earlier quoted context omitted.

> it very nearly caused 2 accidents for me this weekend This wouldn't have been accidental, it would have been fully your own fault for negligence. I'll fully admit this is a pedantic tangent but it's been long acknowledged that "accident" is a problematic word to describe vehicle crashes because it minimizes the agency of a driver and intentional decision making processes that lead up to a crash (for instance, using…

When I was 16, my driver's ed teacher would correct us anytime somebody used the word accident . He insisted on using the word collision instead.

Driving off the road ain't a collision if you don't collide with anything, but it's still an accident.

I agree with you, but that ain't a great word either.

I'd like to have a word that also includes did-not-cause-accident-by-luck failures, such as running a red light or failing to notice a bicyclist who slammed brakes to avoid you sideswiping them.

Best I can offer is "incident".

Re: Why Google's bookmark manager and Docs have purposefully bad UI

#134
post #100
post #94

I’m honestly very okay with this “search-first” mentality the author claims Google promotes. I’ve never organized my photos anymore thanks to Google Photos amazing search, no more time wasted organizing windows media player albums like in the old times thanks to Spotify, I never organize my notes on Notes app but can always find old stuff, my Google Drive is a bit more organized but still I basically go by recent ite…

Nice, but please tell how am I supposed to search for bookmarks I made in japanese section of xvideos? we are just so overwhelmed with information nowadays it’s impossible to keep organizing it, why not let machines just find what we want whenever we need them Then you don’t need bookmarks. You bookmark for a reason, and one of these is that you may not remember exact wording and use other cues like when you did it,…

> one of these is that you may not remember exact wording

that’s exactly the reason to have a good search, I usually always remember a word or at least the general idea of what the thing I’m trying to find was about, a good enough search like Google understand meaning, even if I don’t use the exact words

> please tell how am I supposed to search for bookmarks I made in japanese section of xvideos?

I don’t know, how does xvideos or YouTube does it? You do the same, but with a very limited corpus of just your bookmarks it will be way easier

Re: Why Google's bookmark manager and Docs have purposefully bad UI

#135

Flip side - Google Keep. To search for a note you have to press the search box twice . First time you just get types of things - if you want to search free text you have to press again. I'd argue that UI encourages using tags over search. It's honestly my only major annoyance about Google Keep.

You don't need to press the search box twice. Focusing the search box renders a tag view, but once you start typing it will search free text.

Works on desktops, thanks! Think I was confused because on tablets you still have to pass twice to get the virtual keyboard to come up.

Re: Why Google's bookmark manager and Docs have purposefully bad UI

#136
post #24

Flip side - Google Keep. To search for a note you have to press the search box twice . First time you just get types of things - if you want to search free text you have to press again. I'd argue that UI encourages using tags over search. It's honestly my only major annoyance about Google Keep.

Isn't keep an abandoned project? I use it daily and it doesn't seem to have gotten an update in years (if ever since launch). >It's honestly my only major annoyance about Google Keep. I definitely have more annoyances - it can be slow, it has only minimum features, you can't change the ordering etc.

Guess I'm happy with the minimal features :-) basic notes, syncs across devices, I use a Google account anyway and my notes appear in Google takeout for backup/export purposes.

Re: Why Google's bookmark manager and Docs have purposefully bad UI

#137
post #90

Earlier quoted context omitted.

What did you replace your tab homepage with? Anything in particular to call out?

I wrote my own local .html file, in a local unpackaged extension for Chrome to accept it. It was just four columns of links with favicons and multiple headings per column, and inline inputs to quickly search different sites, and modifier-less keyboard shortcuts like “h” so that you could hit Ctrl-T H to go to HN. The trick, if you can call it that, was that the layout was clear enough that you could pick between 30-5…

Cool, I think I understand what you mean - sounds like a neat experience. I didn't know that was possible. Thanks for the explanation!
Post reply on HN