Google also debuted a new Driving Mode on Google Maps that... entirely changes the UI of of the app and several parts of the phone interface itself. I have never had to look at my phone while driving more in my entire life. It's my fault for using the phone, but it very nearly caused 2 accidents for me this weekend as I tried to get google maps to update or display a particular UI. I truly wonder what is going on ove…
Why Google's bookmark manager and Docs have purposefully bad UI
21–30 of 137 posts
Re: Why Google's bookmark manager and Docs have purposefully bad UI
#22Google also debuted a new Driving Mode on Google Maps that... entirely changes the UI of of the app and several parts of the phone interface itself. I have never had to look at my phone while driving more in my entire life. It's my fault for using the phone, but it very nearly caused 2 accidents for me this weekend as I tried to get google maps to update or display a particular UI. I truly wonder what is going on ove…
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 an app to navigate instead of being better acquainted with your route ahead of time):
https://laist.com/news/car-crash-accident-traffic-violence-l...
Re: Why Google's bookmark manager and Docs have purposefully bad UI
#23Flip 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.
Me: I want a coffee shop.
Maps: Ok let me zoom out and show you coffee shops in a 20km radius.
So you have to zoom back in and “Search this area”. But hey the Starbucks next door is not shown, it’s maddening.
Google’s core business is now ads, not search.
Re: Why Google's bookmark manager and Docs have purposefully bad UI
#24Flip 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.
>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.
Re: Why Google's bookmark manager and Docs have purposefully bad UI
#25Google also debuted a new Driving Mode on Google Maps that... entirely changes the UI of of the app and several parts of the phone interface itself. I have never had to look at my phone while driving more in my entire life. It's my fault for using the phone, but it very nearly caused 2 accidents for me this weekend as I tried to get google maps to update or display a particular UI. I truly wonder what is going on ove…
Not to mention Google Maps gives you about 1/2" x 1/2" of actual map - the rest of your screen is full of other junk.
Re: Why Google's bookmark manager and Docs have purposefully bad UI
#26Re: Why Google's bookmark manager and Docs have purposefully bad UI
#27This would be fine if Google Drive/Docs search wasn't unusably bad
Re: Why Google's bookmark manager and Docs have purposefully bad UI
#28macOS takes the same approach with Finder however. Managing files in macOS is a huge pain if you want to keep it in some nicely organized tree. Its optimized for just searching to find what you're looking for. It presents all files in a flat list by default. Apple's primary business model is not search, so there could be some evidence that more people just prefer search over tags/folders/icons etc.
Re: Why Google's bookmark manager and Docs have purposefully bad UI
#29This is assuming malice when you could assume incompetence (to whatever slight degree this stuff is). Probably these things got put in a future release, or are in the backlog still. Well meaning product designers wanted them and can't have them or some other typical big-co reason a product gets little iteration.
>typical big-co reason a product gets little iteration. That they DGAF if they're not facing competition. IE6 was the same. Threaten them with loss of market share and they'll fix these things.
I would guess it has to do with what I have heard is the promotion path at Google. It seems you need to ship, and ship new things, if you want to be a serious contender. That leaves few engineers willing to take a look at Google Sheets issues and put together a PR to fix these things.