Hacker News new | ask | show | jobs
by flxmglrb 4937 days ago
I think there is some "vocal minority" stuff going on here, particularly with regard to the look and feel of Google's app.

For starters, far from being "fluid", Google's app consistently has a much lower framerate when scrolling or adjusting zoom level than Apple's maps app. It never even approaches 60fps even when running on the latest hardware, whereas Apple's old (and new) map application has always been really good about this, even on old & low-end hardware. So I'm really confused as to what people are talking about when they say it's "fluid". Compared to what?

As for the UI, the way Google's search input bar is positioned actually results in more of the screen being wasted than Apple's standard search bar UI. Those little slivers of the map which stick out above and on the sides are too small to be useful, so what's the point? Just pin it to the top of the screen and make it standard height like all the other apps do, thus giving the maximum amount of contiguous real estate to the actual map itself. There is a reason why Apple does it the way they do, and it's not just for looks.

I have mixed feelings about the detail view being at the bottom. I understand the idea of one-handed operation and I appreciate what they're trying to do here -- optimize for the case of browsing search results with your thumb via a combination of horizontal and vertical swipes, however I'm dubious of the value of it since you still sometimes have to reach awkwardly across the screen for certain things. Not to mention the detail view takes up more real estate than necessary, much like the search bar. It also feels somewhat disconnected from the currently selected pin due to being at the bottom, which is a problem Apple doesn't have since they put the details directly on the annotation.

Oh and of course you cannot blink without this app bugging you to log in.