RescueTime
a demonstration site maintained by RescueTime, Inc.

A Reference Implementation of the RescueTime Analytical Data API

Our API allows read only access to your data, or to someone's or some group's data, should they decide to share it with you. A lot of the hard number crunching is already done for you, but you can take it and merge, calculate, shuffle, regraph as interests you. Currently we offer an embeddable charts JavaScript API, a Python API for general data access, and a implementation using this API on Google's Appengine (this site). Links to download below. Please read the API docs for detailed information.


position: x: time by hour y: social networking
size: efficiency

chart loading...

position: x: time by hour y: use of google stuff
size: efficiency

chart loading...

position: x: time by hour y: efficiency
size: variability of productivity

chart loading...

  1. All the above and bottom left are various statistical munchings of four different data sets from the API. The results are only for RescueTime employees for the last 10 days, so it's a small data set. You'll see odd data on weekends. How we score activities in the RescueTime application infuences the efficiency numbers. Left origin X-axis is farthest in past. All Python (downloadable) using Google Charts API on Google Appengine using appengine-patch for Django, and the RescueTime python and http query APIs.
  2. Above left: we observe if activity in social networking correlates to average productivity (efficiency) over time. There seems to be in general little correlation. Some are efficient while still active in social networks, some not.
  3. Above center: we observe if use of Google's app tools (and some dev tools-- the list will be adjusted over time) influence efficiency over time. There seems to be moderate correlation, with some noticeable positive influence; high use = always efficient, low use = unpredictable.
  4. Above right: In one hour, does flipping between very differently scored activities adversely affect productivity? It seems to at the peaks, but the data shows it's possible to remain mostly efficient despite high variability.
  5. Below left: Data merged to overview categories, ranked by time spent. This data is just raw JSON as delivered by the API, laid out in a table with JavaScript. The fetch is server side, not in AJAX, to protect the access key.
  6. Below right: live data rendered using the embeddable charts feature. This javascript, and scoped data privilege (limited to only what you see here), is obtained with just a click-cut-paste from our reporting views.

Rank Category Hours Active Members