How on earth would you come to think that?
I know you're being facetious, but this is just too far away from reality that it makes no sense. If it's about Apple, I could see it, but Google? No way.
it's worse with their latest "Material" design guidelines applied to the Play Store, as if I
a). work on desks with construction paper representations of all my paperwork
b). have some intuitive understanding of how things slide, uncover, and cover each other elastically when I move them around which I can
c). take with me to my phone experience and go OH OF COURSE THIS IS HOW IT WORKS
Doesn't help that they hide the useful information like date-last-updated or apk-size behind this fancy sliding animation that requires user interaction, instead of directly on the app page.
They need to put someone anal about this stuff like me in charge with the authority to override stupid decisions like closing action-overflow-bar in Chrome because you clicked back/forward once. If you only wanted to go back one, you would have dragged down from the menu, not tapped it. If you opened it, you are going to want to go back or forward more than once, so leave it open while the previous page renders in the background. Oh? That's not the page? Back once more. And again. There we go. Close action bar.
The last UI design that was useful was Windows2000's/XP's Windows Explorer. Carryover from IBM's OS/2 designers, the keyboard shortcuts to navigate are a complete breeze. F6 changes focus consistently in a consistent manner, and bounces between the file/folder selection pane and the folder-path bar twice so that when you are holding it down and miss it due to auto repeat, you press F6 once more and it's up there at the folder-path bar again. No wasted space, and always showed you the filesize in the status bar.
vs. Windows 7 where there's a fat, 3 lines high status bar that tells you THIS IS AN MP3!!!! but doesn't tell you bitrate or filesize, the two things you care about with MP3s.
In short, nothing is power user friendly anymore
So far Google has implemented about 2/3rds of my "Send Feedback" UI suggestions. The most important one so far has been reversing the Google Maps zoom in/zoom out mapping, it used to be double-tap-hold-drag-up to zoom in on the map. This makes little sense when you're zooming in, as your finger is covering the middle of the screen, the part of the screen displaying the most relevant information you're looking for-- the smaller streets that weren't being rendered, the name of the street, i.e. things you're usually looking for when you zoom in. When you're zooming out, you care about the big picture, these details are not important, you just want a rough idea of where you are in the city. About a month after I suggested that the next update had the suggestion implemented, so that it's double-tap-hold-drag-down to zoom in-- removing your finger from blocking the view while zooming in.
However, they still haven't increased zoom in/out sensitivity for this double-tap-hold method-- they must live in a smallish city-- the Yelp app got it right, you can go from almost fully zoomed to complete-city-view in one wipe; I have to paw at Maps about 3 times to get the view I want. Not to mention that something like this should be a consistent experience framework-wide-- should not differ between apps.
Oh and the rendering is still really glitchy. It used to be so much smoother in Maps v6.
And after navigating, it keeps taking your maps view back to isometric mode with direction-of-travel used to orient the map, not True North, and double tapping the compass doesn't always bring it back to True North, sometimes prefers compass-north. I understand this for Navigation, but nobody who looks at a map looks at it at either a 120 degree angle or rotated 90 degrees when they're trying to find either a destination or their current location in relation to destination. Doing so is divergent from the whole Material Design UI recommendation.
Ugh. It makes me want to die
Facebook
Twitter