prox
prox copied to clipboard
Add & verify telemetry probes
Initial comments: collect the same data we did in Hawaii.
I’ve been thinking about solving some problems with analytics in a document called Detecting Activities.
The gist of my proposal was to correlate some of the data that we’re already planning to collect (under the heading “Optional for Prox v2”) and some new data:
- (Item 11) What individual cards in the Home view are being viewed?
- (Item 12) What cards serve as user session end points? (i.e. cards where they click on a link for directions)?
- (New) How many users ended up actually arriving (being in the proximity of) at a place after tapping “Get directions”?
- (New, but for the future) What places get rated (using third-party app, connected to Prox) after a visit?
TL;DR – We should add telemetry probes for which cards are viewed in the app, and which cards are visited in real life.
By collecting this data, I argued that we’d be able to augment our default sort order. Instead of sorting by proximity, we can prioritise cards with the same same category as:
- Cards you’ve highly rated in Yelp, TripAdvisor and/or Foursquare
- Cards you’ve physically been to
- Cards where you’ve tapped “Get directions”
- Cards that you’ve spent a lot of time viewing/engaging with