April 10

We can be a bit … competitive around here

I’m a little bit of a usability and data architecture nerd. I hate it when an interface doesn’t work well, or there’s information stuck some place that can’t get some place else. When it all comes together, it’s a joy.

But that interest is secondary to my ingrained competitive spirit.

Anything you can do, I can do better …

Picture a quiet Easter Sunday afternoon. I’m in the car with a friend and we’ve got our near-matching iPhones at the ready. The goal? Find out what stores are open that carry the perfect water shoes for knee-deep island landings. The real goal? Beat the other guy at finding out what stores are open.

One of us used an Apple app, the other a Google app. Both of us got the same basic information … Name of the store, distance, time to drive, address, website, phone number, hours …

But the Google app’r had superior NAP data. This is something Google very very recently expanded, and is very very useful. While the Apple app’r was still making phone calls, the Google app’r was ready to go, armed with some pretty awesome local and holiday-specific info.

I’m glad this is something businesses can use, and big national businesses are using well (or poorly) …

It saved the Google app’r a lot of dialing to businesses that were not open, driving to businesses that were not open, and aggravation. We went straight to the store we wanted — and yes, dear reader, we did find the perfect water shoes.

Note: All images are simulated because we were too busy squaring off forgot to take screenshots right then.

image of map and data shots from navigation apps
When two apps want to share data very very much …


Copyright © 2014-2017. All rights reserved.

Posted April 10, 2016 by Lorena in category "Apple", "Data Architecture", "Google", "User eXperience