New iOS Update: Upload Profile Pictures!

Hmmm. Ok, I think I’m getting there slowly (and sorry if I’m coming across as a bit thick here)… but what is the result of matching the user’s location to Google’s merchant data? Isn’t the merchant identified as a result of the transaction?

I guess what I’m getting at is, and if I look at a transaction example in the app, I see a number of things:

The location, marked with a pin on a map (in this case one cached from Google), which is achieved through the LON+LAT info;
The merchant name, which is derived from the transaction data itself;
And the merchant’s logo, which I believed is pulled from their avi on social media (twitter?) if it exists.

What specifically requires Google’s merchant data?

OK. So, I’m by no means an expert in this but:

  1. User makes purchase
  2. We get some information from Mastercard — things like a garbled merchant name and partial postcode
  3. We use the Google Places database to make that into a full merchant — proper name, exact location etc.
  4. We also use a few other services to enrich this (Foursquare, Twitter) etc. to bring in logos
  5. We cache that info on our servers
  6. On device, we draw Google Maps to show that info we’re now caching

That’s my understanding anyway. @james or @matt can correct anything I’ve got wrong :slight_smile:

5 Likes

If this was an option, I’d also expect to see the option for giving old Ordnance Survey map grid references as an alternative too. :joy:

Google Maps > Apple Maps :smirk:

I would imagine that nothing currently NEEDS Google’s merchant data in the iOS UI but in the future they’ll be able to get the UI to show the place, rather than just the location.

This means you’ll be able to get all the enriched Google Places data in the client, such as opening times, contact details, current busyness of the location/expected future busyness, Street View and other photos, reviews, integration with menus, ordering and other custom business information such as what it’s good at and other related businesses/competitors, etc., etc.