IntroductionYou know what's awesome? Pocket.
I mean, sure, it's not the first. I think Instapaper existed a little before (perhaps). And there are alternatives, like Google Reader. But Pocket is still my favorite. It's pretty awesome at what it does.
Pocket (or Read It Later, as it used to be known) has fundamentally changed the way I read.
Before I had an Android phone I used to primarily read books. But applications like Pocket allow you to save an article from the web so you can read it later. Being a big fan of reading (and also procrastination) this was a really great application for me to discover, and I'm quite glad I did. Now I can still catch up on the latest Lifehacker even if I am on the subway and don't have data connectivity.
BackgroundThe other interesting thing about this application is that they make it fairly easy to get a hold of your data. The website has an export function which allows you to dump all your data for everything you've ever added to your reading list into HTML.
Having the URL of every article you've ever read in Pocket is handy, as you can revisit all the articles you've saved. But there's more to it than that. The HTML export also contains the time each article was added (in UNIX epoch). Combine this with an XML or JSON dump from the API, and now we've got some data to work with.
My data set comprises a list of 2975 URLs added to the application over the period 14/07/2011 - 19/09/2012. The data from the export includes the article ID, article URL, date added and updated, and tags added to each article.
In order to add to the data provided by the export functionalities, I wrote a simple Python script using webarticle2text, which is available on github. This script downloaded the all the text from each article URL and continually added it to a single text file, as well as doing a word count for each article and extracting the top-level domain (TLD).
AnalysisFirst of all we can take a very simple overview of all the articles I have saved by site:
Also, I think this is largely due to the design of the site. I commented before that using Pocket has changed the way I read. Well, one example of this is that I find I save a lot more articles from sites which have well designed mobile versions, as I primarily add articles from my phone. For this reason I can also see why I have saved so many articles from Psych Today, as their well-designed mobile site has made it easy to do so. Plus the article titles are usually enough to grab me.
You can have a look at their visually appealing mobile site if you are on a phone (it detects if the browser is a desktop browser). The other top sites in the list also have well-designed mobile sites (e.g. The Globe and Mail, AskMen, Ars Technica).
Good mobile site design aside, I like reading psych articles, men's magazines, news, and tech.
Next we examine the data with respect to time.
Unfortunately the Pocket export only provides two categories: time added and time 'updated'. Looking at the data, I believe this 'updated' definition applies to mutiple actions on the article, like marking as read, adding tags, re-downloading, et cetera. It would be ideal to actually have the date/time when the article was marked as read, as then further interesting analysis could be done. For example, looking at the time interval between when articles were added and read, or the number the number of articles read per day.
Anyhow, we continue with what data are available. As in a previous post, we can get a high-level overview of the data with a scatterplot:
You can also see the general usage lining up with events in my personal life. The bands start in early October, shortly after I began my new job and started taking public transit. There is also a distinct gap from late December to early January when I was home visiting family over the Christmas holidays.
You can see that as well as being added while I am on public transit, articles are also added all throughout the day. This is as expected; I often add articles (either on my phone or via browser) over the course of the day while at work. Again, it would be interesting to have more data to look at this further, in particular knowing which articles were read or added from which platform.
I am uncertain about articles which are listed as being updated in the late hours in the evening. Although I sometimes do read articles (usually through the browser) in these hours, I think this may correspond to things like adding tags or also a delay in synching between my phone and the Pocket servers.
I played around with heatmaps and boxplots of the data with respect to time, but there was nothing particularly interesting which you can't see from this scatterplot. The majority of articles are added and updated Monday to Friday during commute hours.
We can also look at the daily volume of articles added:
This graph looks similar to one seen previously in my post on texting. There are some days where very few articles are added and a few where there are a large number. Looking at the distribution of the number of articles added daily, we see an exponential type distribution:
Lastly we examine the content of the articles I read. As I said, all the article text was downloaded using Python and word counts were calculated for each. We can plot a histogram of this to see the distribution of the article length for what I've been reading:
Well, that doesn't look quite right. Did I really read an article 40,000 words long? That's about 64 pages isn't it? Looking at URLs for the articles with tens of thousands of words, I could see that those articles added were either malfunctions of the Pocket article parser, the webarticle2text script, or both. For example, the 40,000 word article was a post on the Dictionary.com blog where the article parser also grabbed the entire comment thread.
Leaving the data as is, but zooming in on a more reasonable portion of the histogram, we see something a little more sensical:
This is a little more what we expect. The bulk of the data are distributed between very short articles and those about 1500 words long. The spikes in the low end also correspond to failures of the article parsers.
Now what about the text content of the articles? I really do enjoy a good wordcloud, however, I know that some people tend look down upon them. This is because there are alternate ways of depicting the same data which are more informative. However as I said, I do enjoy them as they are visually appealing.
So firstly I will present the word content in a more traditional way. After removing stop words, the top 25 words found in the conglomerate file of the article text are as follows:
As you can see, there are issues with the download script as there is some garbage in there (div, the years 2011 and 2012, and garbage characters for "don't" and "are", or possibly "you're"). But it appears that my recreational reading corresponds to the most common subjects of its main sources. The majority of my reading was from Psychology Today and so the number one word we see is "people". I also read a lot articles from men's magazines, and so we see words which I suspect primarily come from there ("women", "social", "sex", "job"), as well as the psych articles.
And now the pretty visualization:
Seeing the content of what I read depicted this way has made me have some realizations about my interests. I primarily think of myself as a data person, but obviously I am genuinely interested in people as well.
I'm glad data is in there as a 'big word' (just above 'person'), though maybe not as big as some of the others. I've just started to fill my reading list with a lot of data visualization and analysis articles as of late.
Well, that was fun, and somewhat educational. In the meantime, I'll keep on reading. Because the moment you stop reading is the moment you stop learning. As Dr. Seuss said: "The more that you read, the more things you will know. The more that you learn, the more places you'll go!"
- Majority of reading done during commute on public transit
- Number of articles added daily of exponential-type distribution
- Most articles read from very short to ~1500 words
- Articles focused on people, dating, social topics; more recently data
ResourcesPocket (formerly Read It Later) on Google Play:
Pocket export to HTML:
Mediagazer Editor Lyra McKee: What’s In My Pocket
Founder/CEO of Pocket Nate Weiner: What's In My Pocket
Pocket Trends (Data analysis/analytics section of Pocket Blog)
webarticle2text (Python script by Chris Spencer)