{"id":13813,"date":"2012-11-21T10:43:17","date_gmt":"2012-11-21T14:43:17","guid":{"rendered":"http:\/\/blumenthals.com\/blog\/?p=13813"},"modified":"2012-11-21T18:16:30","modified_gmt":"2012-11-21T22:16:30","slug":"nokia-here-maps-sucks-significantly-more-than-apple-maps","status":"publish","type":"post","link":"https:\/\/blumenthals.com\/blog\/2012\/11\/21\/nokia-here-maps-sucks-significantly-more-than-apple-maps\/","title":{"rendered":"Nokia HERE Maps Sucks (Significantly) More Than Apple Maps"},"content":{"rendered":"

\"\"<\/a>Nokia, with the help of Navteq, is a seasoned mapping company. Arguably they are in the top tier of digital mapping. Their new product, Nokia HERE Maps for the iPhone, should show Apple what good mapping is all about. It doesn’t. In fact basic interface issues prevent the product from being a serious contender in the iPhone navigation market. Apple can now proudly say that there is a mapping product for the iPhone that sucks more than theirs.<\/p>\n

Visuals<\/strong>: When I read reviews<\/a> online about it being blurry, slow, ugly and lacking turn by turn, I couldn’t believe that Nokia would put out an inferior product. Now is the time to strike while Apple is still recovering from their Maps fiasco and come out with a great product. I thought Apple fan boys were just ranting. I particularly could not understand a map that was blurry. But sure enough the maps are totally fuzzy, hard to read and annoying. The ONLY thing clear on the map was the “here” brand name. And as Andrew Shotland pointed out<\/a> even that can be confusing in the context of a map.<\/p>\n

Basic Interface Screw Ups<\/strong>: My first search was for 1 Riverside NY, NY. A search that both Apple Maps and Google Maps understands. Apparently Nokia HERE does not understand common abbreviations like NY for New York. When searching for NY it turned up a foreign airport who knows where. When I searched on SF, CA it turned up Santa Fe, New Mexico. Forcing users to type out every word on an iPhone is a big hurdle from the get go and not understanding common naming short cuts is a deal breaker.<\/p>\n

Kludgey Interface<\/strong>: Generally the interface for anything other than basic directions is confusing. Certain tasks like looking up nearby business are totally opaque and often non functional. I searched for nearby Grocery stores and was shown a department store.<\/p>\n

Business Listing Quality<\/strong>: As far as I can tell other than certain categories like food, entertainment and shopping these are missing altogether.<\/p>\n

Routing<\/strong>: I do not live in a big city so my tests typically reflect testing a product’s familiarity with back roads and short cuts. I figure if the product can get these back country roads correct far away from urban centers then the chance of getting the more important stuff right is far higher. Apple and Google both gave me a choice of routes although Apple gave the better choices and in its current iteration, a better way to select the route. HERE offered no such options and offered no alternative routing. It was their route or the highway so to speak.<\/p>\n

Things Nokia HERE Has<\/strong>: It does offer public transportation routes which Apple does not. For me that is not enough to get by the egregious interface issues. They also offer the option to save a map for offline use, although the many warnings and caveats were discouraging. A map can take up to 13 mbytes of storage.<\/p>\n

Bottom Line<\/strong>: Don’t waste your time or bandwidth to download the product unless it is for a case study in the decline of Nokia as a force in the mobile world.<\/p>\n

Some additional screen shots comparing Apple Maps & HERE Maps output (click to see images at full resolution):<\/p>\n