Google Releases Windows Phone App for Google Reader

Google is about to launch its second Windows Phone app. This time, Google picked a service that was used by a few million users until it was discontinued last year: Google Reader.

While the new app won't be able to show the latest news from your feeds, it's a clear sign that Google started to embrace Microsoft's mobile platform. Apparently, Google was about to launch the app in January 2013, but developers were busy updating Google's apps for Android and iOS. A week ago, someone found the app and decided it's a good idea to release it. The application lets you login to your Google account and shows this message: "Google Reader has been discontinued. We want to thank all our loyal fans. We understand you may not agree with this decision, but we hope you'll come to love these alternatives as much as you loved Reader."

It's simple, minimalist and pretty late, just like Windows Phone.

Google Reader Backup Viewer

If you created a full backup for your Google Reader account while it was still possible, you probably need a way browse the data. Fortunately, Mihai Parparita created Zombie Reader, a tool that resurects the Google Reader interface and transforms into a viewer for your data.

"Reader is a canonical single page application: once the initial HTML, JavaScript, CSS, etc. payload is delivered, all other data is loaded via relatively straightforward HTTP calls that return JSON (this made adding basic offline support relatively easy back in 2007). Therefore if I served the archived data in the same JSON format, then I should be able to browse it using Reader's own JavaScript and CSS," says Mihai.

Go to readerisdead.com, download the updated archive and use the instructions from the page. You still need Python 2.7 and some basic command-line skills. For Windows, you could use the instructions from my previous post and replace:

DOWNLOAD 

with

c:\python27\python zombie_reader\zombie_reader.py download

Zombie Reader uses the Google Reader interface and your local data. It's like a Google Reader snapshot that preserved all your subscriptions, all the items you've read or marked as read, all your starred items, your tags and much more. Obviously, many features don't work (search, trends, subscribe), the application doesn't save your state and it doesn't show the latest posts from your subscriptions.

It does show your first read item, first starred item and the first shared item, as well as the people you followed before Reader's social features were removed. The "sort by oldest" feature is no longer limited to the last 30 days, it now sorts all your feed items.

"A side effect is that I now have a self-contained Reader installation that I'll be able to refer to years from now, when my son asks me how I spent my mid-20s," says Mihai. "It also satisfies my own nostalgia kicks, like knowing what my first read item was. In theory I could also use this approach to build a proxy that exposes Reader's API backed by (say) NewsBlur's, and thus keep using the Reader UI to read current feeds. Beyond the technical issues (e.g. impedance mismatches, since NewsBlur doesn't store read or starred state as tags, or has per item tags in general) that seems like an overly backwards-facing option." I'm sure that someone will build the proxy.

Google and Feeds

For some reason, a day before Google Reader was closed, Google Developers blog published an article about PubSubHubbbub, feeds and the Google Feeds API. PubSubHubbub (PuSH) is a protocol for sending notifications when a feed is updated. "Using the PuSH protocol, servers can subscribe to an almost arbitrarily large number of feeds and receive updates as they occur." Google encourages publishers to submit their feeds to a public PuSH hub like Google's hub and Superfeedr's Open PubSubHubbub Hub.

The most interesting part of the post is this one: "Google directly hosts many feed producers (e.g. Blogger is one of the largest feed sources on the web) and is a feed consumer too (e.g. many webmasters use feeds to tell our Search system about changes on their sites). Our PuSH hub offers easy access to hundreds of millions of Google-hosted feeds, as well as hundreds of millions of other feeds available via the PuSH ecosystem and through active polling." And something else: "We are planning some improvements to the Feed API, as part of our ongoing infrastructure work."

This means that Google's feed processing backend will continue to exist, but will focus on the Google Feeds API and Google Search index updates. Google Feeds API will also continue to exist and third-party feed readers could use it. All of this was an important part of the Google Reader backend, but Google Reader also had to manage subscriptions, labels, the read/unread state, create a search index for each user.

Hopefully, this also means that Google's services will continue to offer feeds. Maybe, at some point, even Google+ could add support for feeds.

Update: Google Feedfetcher is still running and shows almost the same number of subscribers. Here's a screenshot from FeedBurner:

"Feedfetcher is how Google grabs RSS or Atom feeds when users choose to add them to their Google homepage or Google Reader. Feedfetcher collects and periodically refreshes these user-initiated feeds, but does not index them in Blog Search or Google's other search services (feeds appear in our search results only if they've been crawled by Googlebot)." - from Google's help center.

Tomek Wasiak noticed Google Feedfetcher in his site's logs today. He subscribed to the site's feed in Google Reader and he's the only subscriber.

Google Alerts Drops RSS Feeds

If you read the post about the well-connected Google Reader, you probably anticipated this chain reaction. All the services that integrated with Google Reader will remove their features, now that Reader is gone.

Google Alerts no longer supports RSS delivery and recommends users to switch to email delivery. "Google Reader is no longer available. To continue receiving Google Alerts, go to http://www.google.com/alerts/manage and change your alerts to email delivery," says Google.

You're probably wondering: what's the connection between Google Alerts feeds and Google Reader? Google Alerts feeds, which were added back in 2008, had public URLs and you could use any feed reader to subscribe to them. The trouble is that the feeds were generated by Google Reader and were actually a Google Reader feature, just like the web page monitoring feature.

Unfortunately, Google doesn't offer feeds for search results and the Web Search API has been deprecated and it was too limited to create a service like Google Alerts. The only obvious alternative is to screenscrape Google results.

Talkwalker Alerts looks almost like Google Alerts and offers both email alerts and feeds. The service is free for up to 100 alerts.

Google Reader's Final Message

If you open Google Reader, you'll see this message:

Thank you for stopping by.

Google Reader has been discontinued. We want to thank all our loyal fans. We understand you may not agree with this decision, but we hope you'll come to love these alternatives as much as you loved Reader.

Sincerely,

The Google Reader team

Frequently-asked questions

What will happen to my Google Reader data?

All Google Reader subscription data (eg. lists of people that you follow, items you have starred, notes you have created, etc.) will be systematically deleted from Google servers. You can download a copy of your Google Reader data via Google Takeout until 12PM PST July 15, 2013.

Will there be any way to retrieve my subscription data from Google in the future?

No -- all subscription data will be permanently, and irrevocably deleted. Google will not be able to recover any Google Reader subscription data for any user after July 15, 2013.

Why was Google Reader discontinued?

Please refer to our blog post for more information.

I don't understand why Google removes Reader data so soon and why the message uses words like "systematically deleted", "permanently, and irrevocably deleted". It's like they try to get rid of everything that's related to Reader. I can still download Google Buzz data from Google Takeout. A similar message was posted for Google Health, but users had one year to download their data.

The End of This Internet

"Congratulations, you've reached the end of this internet. Look for another?" That's the message you see when you use the Google Reader bookmarklet and you read all the posts from your subscriptions. It's a joke that's quite bitter, now that the end of Google Reader is really close.

Google Reader was more than just a feed reader, it was probably the most well-connected Google service. It was integrated with so many Google services and now all of them will be a little less useful. The missing features, which relied on Google Reader, will show how important this service really was.

iGoogle's canvas view for feeds was powered by Google Reader and now it's no longer available, just like the Reader gadget.

Full Google Reader Backup

"Reader is dead," says Mihai Parparita, one of the former Google Reader engineers. You still have 2-3 days to use Google Reader, but the best thing you can do is to export your data.

Google Takeout lets you export some of your Reader data, but not everything: your subscriptions, your notes, starred items, shared items, liked items, the list of followers and the people you were following, the items shared by the people you were following. Mihai Parparita wrote some Python scripts that download everything from your Google Reader accounts, including the entire content of the posts from your subscriptions. You need Python 2.7, some basic command-line skills and a lot of free storage: my backup has more than 5 GB for about 250 feeds (vs 125 MB for the uncompressed Takeout backup).

Here are some tips for running the script in Windows 7/8:

- install Python from here (Python 2.7.5 Windows Installer)
- download Mihai's zip file and extract the files
- open the folder in Windows Explorer and you should see a list of subfolders like "base", "bin", "feed_archive".

- Shift + right-click below the folders and select "open command-line window here".
- copy this code, paste it in the command-line window and press Enter (I assumed that Python's folder is c:\python27):

set PYTHONPATH=%cd%
c:\python27\python reader_archive\reader_archive.py --output=download

- a web page will open in your favorite browser and you'll need to click "Accept", copy the authorization code and paste it in the command-line window.
- wait until the script downloads all the files.

Mihai also started to write a script that lets you browse your archive. It's a work in progress, probably because the script for downloading your data is more important right now.

There's also a script for downloading a feed's archive. "Google Reader has (for the most part) a copy of all blog posts and other feed items published since its launch in late 2005 (assuming that at least one Reader user subscribed to the feed). This makes it an invaluable resource for sites that disappear, can serve as a backup mechanism and enables tools to be created." My post from 2007 provides another way to download the history of a feed. You can also upload your OPML file to this site, which preserves hitorical feed data.

"I don't fault Google for providing only partial data via Takeout. Exporting all 612,599 read items in my account (and a few hundred thousand more from subscriptions, recommendations, etc.) results in almost 4 GB of data. Even if I'm in the 99th percentile for Reader users (I've got the badge to prove it), providing hundreds of megabytes of data per user would not be feasible. I'm actually happy that Takeout support happened at all, since my understanding is that it was all during 20% time," says Mihai Parparita, who spent 5 years working on Google Reader.

If you're curious to know which Reader alternative gets a thumb up from Mihai, his answer is "a toss-up between NewsBlur and Digg Reader."

The Feed Reading Playground Is Now Open

Google used this many times last year: "the playground is open". That's one of the most important things about Android: it's open source and any company can use it. One of the definitions of "open" is "accessible to all, unrestricted as to participants".

The playground for feed readers is now open. Google Reader's demise levels the playing field in the feed reading world. Now there are more competitors, there's more innovation, there are new platforms for distributing feeds, new interfaces. Suddenly, feed readers are a hot topic. Until now, Google Reader was the dominant service and platform, but Google didn't know what to do with it. Google Reader stopped adding new features back in 2010 and it was in maintenance mode ever since then. Few dared to challenge its position and most new feed readers were only Google Reader clients.

Google Reader's disappearance is Google's best idea for saving RSS. From stagnant to vibrant in 3 months - Google Reader's demise helped RSS more than the last 3 years of silence. The playground is now open.

And for those who are sad that Reader will soon be gone - don't worry, there's a bit of Google Reader in any feed reader that has launched in the past 3-4 years or will launch in the near future. Maybe it's time to get a better Reader, even if not from Google...

A Google Reader Puzzle From 2007

Back in 2007, Google accidentally made public an internal video about Google Reader. The video included a lot of useful information about Google Reader, the kind of details you'll never find in a Google post or presentation.

I'm trying to solve the puzzle and find the number of Google Reader users from 2007. Here are the hints:

1. At that time, Google Reader crawled 8 million feeds.

2. Two thirds of the feeds had only one subscriber, one third of the feeds had more than one subscriber.

3. Google Reader used 10TB for storing all the raw data.

4. The rate of user growth = the rate of growth for the number of feeds.

5. The index size grew 4% every week.

6. 70% of the Google Reader traffic came from Firefox (at that time, Firefox's market share was about 15%).

7. Gmail and orkut were the only Google applications that had a bigger number of pageviews/user than Google Reader.

8. The main Google Blog had 100,000 subscribers and this number includes all the subscribers from iGoogle, Reader and orkut.

So, at that time, only 2.6 million feeds indexed by Google Reader had more than one subscriber. Probably many of the feeds that had only one subscriber were used by other Google services powered by Google Reader's backend (orkut, Blogger widgets, Google Spreadsheets, Ajax API) or they were Google News/Blog Search feeds. It makes sense to assume that the number of Google Reader users was lower than the number of feeds with more than one subscriber.

Here's a chart from 2010 that shows Google Reader's user growth:



And something else from 2010: "the average Reader user reads about 105 items a day".

It's probably worth distinguishing Reader as a service from Reader as a platform.

The Most Well-Connected Google Service

Many people think that Google Reader could've been more successful if Google promoted it more. The truth is that Google Reader has been the service that connected to the biggest number of Google services. No other Google benefited from so many service integrations.

Here's an incomplete list. Start counting:

1. a link to Reader was displayed in Gmail's inbox when there was no mail

2. for many years, Google Reader could be found in the main navigation bar, next to Gmail, Calendar and Google Docs

3. Google Reader was the first Google service that worked offline and the first Google service that used Google Gears, back in 2007



4. Google Reader integrated with Google Social Search, a feature that allowed you to restrict results to the pages written by your friends or people you follow.



5. iGoogle integrated with Google Reader when it started to add support for canvas view. Maximize a feed gadget and you get the Google Reader interface.



6. Blogger's Following feature was powered by Google Reader. "The blogs you follow in Blogger have been added as subscriptions in Google Reader. Subscriptions can be managed in Reader without affecting your following list in Blogger."



7. Listen, Google's podcast manager app for Android, used Google Reader to store subscriptions.

8. Google Alerts integrated with Google Reader, so you could subscribe to feeds instead of receiving email notofcations.

9. Back in 2008, Google's mobile transcoder displayed the site's feeds at the top of the page and linked to Google Reader.

10. Google Reader was the only Google product with an interface optimized for Nintendo Wii.

11. Google Currents, launched in 2011, allowed you to import your Google Reader subscriptions.

12. Google Buzz's commenting feature was integrated with Google Reader.



13. When Bloglines was discontinued in 2010, Google Reader's team encouraged users to switch to Reader. The blog post includes a graph of Reader users over time.

14. The Google Groups redesign from 2010 was inspired by Google Reader.

15. Google bought FeedBurner to monetize Google Reader and launched AdSense for Feeds.

16. Back in 2007, Google Reader made shared items available to Google Talk contacts and many people complained about this.

17. Google's Power Readers feature from 2008 allowed you to "track the news sites and blogs Barack Obama and John McCain read" using Google Reader. It was a clever way to promote Google Reader. This feature was expanded to "include journalists, techies, fashion critics, foodies and more".

18. Google Toolbar for IE allowed you to subscribe to feeds using iGoogle or Google Reader.

19. Google Blog Search still has this link below the list of search results page: "Subscribe to a blog search feed for [query] in Google Reader". Google News had a similar link.

20. Google Spreadsheets has a special function for importing feeds that was initially called GoogleReader. Now it's called ImportFeed.

21. Google TV Queue uses Google Reader to manage subscriptions.

22. Google Reader was Google's infrastructure for feeds and the technology was used by iGoogle, orkut, Gmail's web clips, Blogger widgets, Google Spreadsheets and the Ajax API.

I'm sure you can find other examples of services that integrated with Google Reader. I didn't include all the third-party apps and services that used the unofficial Google Reader API. As you can see, Reader was an important part of the Google ecosystem and Google did promote the service in many ways.

From Google Reader to Feedly

There's just one week and a half and Google Reader will be history. If you're using the service, it's a good idea to export your data and switch to a different service. You can choose from Feedly, The Old Reader, MultiPLX, NewsBlur, Feedspot, Netvibes. I haven't decided which one I'll use, but Feedly is a strong contender.

Feedly is probably the service that will benefit the most from Google Reader's demise. It grew from 4 million users to 12 million users in only 3 months and that's impressive. The service was just a Google Reader client, an alternate interface for Google Reader that gained a foothold on mobile.

Feedly has recently started to migrate users from Google's backend to its own backend, while preserving most of their data. Feedly Cloud was built in record time and it's now a scalable infrastructure for Feedly that can also be used by other apps that were powered by the unofficial Google Reader API. There are 9 apps that use it, including gReader, Newsify and Sprout Social. If you don't like the mobile apps or the browser extensions, there's now a Feedly web app that's optimized for the desktop and replaces extensions. It's hard to morph from a client to a platforms in a few months.

I'll miss Google Reader, like many other power users. Unfortunately for us, Google is not the right company for niche services. Google wants to create products that are used by hundreds of million of users and Google Reader wasn't one of them. Feedly and other similar services will have to find a business model for something that's no longer cool, no longer supported by many browsers, no longer supported by Twitter (other sites to follow). For many people, social sites offer better value than feed readers and not even Google could change that.

"As a culture we have moved into a realm where the consumption of news is a near-constant process. Users with smartphones and tablets are consuming news in bits and bites throughout the course of the day — replacing the old standard behaviors of news consumption over breakfast along with a leisurely read at the end of the day. (...) Google is looking at pervasive means to surface news across products to address each user's interest with the right information at the right time via the most appropriate means," said Richard Gingras, Senior Director, News & Social Products at Google.

So what will you use instead of Google Reader?

Google Reader for Android

Google Reader's mobile web app works really well and it has a great interface, so there aren't many reasons to create a native application for Google Reader. The main issue is that the application doesn't work offline, but this is a feature that could be easily implemented.

Instead of improving the mobile web app, Google decided to release a native Android app for Google Reader. The application supports multiple accounts, synchronizes your subscriptions and works offline. It also lets you search your feeds -- a feature that's inexplicably missing from the mobile web app.


Google Reader for Android uses infinite scrolling, has bigger touch areas, it integrates with the operating system's "send to" actions and has a neat trick in the settings that lets you navigate between articles using your phone's volume keys.

Google Reader's Web Page Monitoring to Be Disabled

Google Reader's blog announced that the feed generator for pages that don't have feeds will no longer be available starting from September 30. Google says that not many people used this feature, which is not surprising, considering that it's quite difficult to find it.

Google Reader's page tracking feature was useful to monitor the web pages that don't have feeds. For example, you could use it to find when Google changes the privacy policy, when Google Chrome adds new extension APIs or when there are new products in the Google Store.

Unfortunately, Google Reader's feeds looked terrible. The title for each item was "generated feed for [URL]", the feature didn't detect new images and the feeds were updated when the new versions of the pages were added to Google's search index. Here's Google Reader's feed for google.com and here are the changes found by Page2RSS. Page2RSS found 8 changes in September, while Google only found one. Page2RSS has another important advantage: the service constantly monitors web pages and it's not tied to a search engine that indexes billions of web pages.

Bloglines to Be Discontinued

Bloglines, one of the most popular web-based feed readers, will no longer be available after September 30th. InterActiveCorp, the company that acquired the service in 2005, also owns the search engine Ask.com.

When we originally acquired Bloglines in 2005, RSS was in its infancy. The concept of "push" versus "search" around information consumption had become very real, and we were bullish about the opportunity Bloglines presented for our users. 
 
Flash forward to 2010. The Internet has undergone a major evolution. The real-time information RSS was so astute at delivering (primarily, blog feeds) is now gained through conversations, and consuming this information has become a social experience. As Steve Gillmor pointed out in TechCrunch last year, being locked in an RSS reader makes less and less sense to people as Twitter and Facebook dominate real-time information flow. Today RSS is the enabling technology – the infrastructure, the delivery system. RSS is a means to an end, not a consumer experience in and of itself. As a result, RSS aggregator usage has slowed significantly, and Bloglines isn't the only service to feel the impact. The writing is on the wall.


Most Bloglines users will probably migrate to Google Reader, which is now the most popular web-based feed reader. Unfortunately, Google Reader is still a niche service and this won't change in the future, so Google will eventually discontinue it. Instead of subscribing to feeds, people prefer to subscribe to other people. Google Buzz, Google Me and other social services will use Google Reader's back-end, while offering a people-centric experience.

Here's the Google Trends chart for RSS:

Comment on Any Google Reader Shared Item

Google Reader simplified the commenting feature so that anyone can comment on a shared item. "Up until now, someone had to be in a designated sharing group to be able to comment on a post, even if you were sharing publicly. To make things a lot simpler, we've made it so that if you can see a shared item, you can comment on it."

An important side-effect is that Google Buzz users can comment on any post shared in Google Reader, assuming that the shared items are connected to a Buzz profile. Since you can now comment on a Google Buzz post by replying to a message in Gmail, you could share a blog post in Google Reader and one of your Buzz followers could post a comment from in Google Buzz and then reply to your answer from Outlook, Thunderbird or from the Gmail mobile app for Blackberry.

If you don't like Google Reader's interface, there are desktop apps like FeedDemon, NetNewsWire or Liferea that import your Google Reader subscriptions and synchronize your actions with Google Reader. That means you could share a blog post in FeedDemon and someone could post a comment from Google Buzz or from an application that uses Google Buzz API.

While people can post comments to a Google Reader shared item in Google Buzz, you'll still see the comments in Google Reader. It's not really important where you find a great article and where you comment.


In other news, Google Reader will drop support for outdated browsers (IE6, Firefox < 3.0, Safari < 4.0, Chrome < 4.0) and will remove the offline mode powered by Google Gears starting on June 1. Why not remove offline support when Google Reader implements the same feature in HTML5?

Disable Google Reader's Social Features

If you don't like Google Reader's social features and you only want to read your subscriptions, you can now switch to the antisocial asocial Google Reader interface:

1. Go to Google Reader

2. Type this JavaScript code in the address bar:

javascript:antisocial('true')

3. Google Reader will reload and you'll see a simplified interface that removes the section "People you follow" and no longer shows shared items from your friends.


The setting is saved to your account, even if the toggle is not included in the interface. To go back to the standard interface, type this code in the address bar:

javascript:antisocial('false')

{ via George Moga }

Google Reader Adds Support for Video and Audio Tags

Google's feed reader started to support the video and audio tags from feeds. The only popular browser that doesn't support the two tags is Internet Explorer, but that doesn't mean that you'll be able to play videos without plug-ins in all the other browsers.

As the screenshot below shows, Firefox and Opera don't support the H.264 compression standard, so you can't play videos from sites that only use H.264. Even if video sites like YouTube or Vimeo started to test HTML5 players, they don't offer the option to embed videos using HTML5 tags.


{ via Google Reader's Twitter page. Thanks, François. }

Bookmarklet for Google Reader Play

Mihai Parparita wrote a bookmarklet that loads the feed for the current site in Google Reader Play. Mihai suggests to use the bookmarklet for web pages that have a lot of photos, like Flickr profiles or comic feeds.


Google Reader Play creates a slideshow from any feed or collection of feeds, but I don't think it's useful as a standalone app. Google Reader could detect photo feeds and integrate Reader Play as a new view.

Google Reader Play

Google Reader Play is a new way to read popular articles and an interesting interface for browsing web pages.

"In Google Reader Play, items are presented one at a time, and each item is big and full-screen. After you've read an item, just click the next arrow to move to the next one, or click any item on the filmstrip below to fast-forward. Of course, you can click the title or image of any item to go to the original version. And since so much of the good stuff online is visual, we automatically enlarge images and auto-play videos full-screen," explains Google.



The interface is optimized for posts that include images and for short blog posts. You can use keyboard shortcuts to navigate to the next post or you can start the slideshow view to only look at the images and headlines.

I was disappointed to see that Google Reader Play doesn't show your subscriptions. It only shows a list of recommended pages and Google uses your actions (starring, liking or sharing items) to improve the recommendations. If you want to read your subscriptions in Google Reader Play, use this URL:

http://www.google.com/reader/play/#stream

Track Page Changes Using Google Reader

Not all web pages offer feeds and sometimes it's useful to monitor web pages and find the latest information. A great service that offer this feature is Page2Rss, which provides a feed for each monitored web page.

A similar feature is now available in Google Reader and it's cleverly integrated: click on "Add subscription", type the address of a web page and Google Reader will automatically generate a feed if it can't detect one.


"We provide short snippets of page changes to help you quickly decide if the page is worth revisiting and we're working on improving the quality of these snippets," says Brian Shih.

"Reader may not always detect updates to your content. Currently, only English-language content in HTML format is supported. In addition, updates to content in frames are not detected; nor are updates to content that requires sign-in to view," mentions a help center article, which also informs that webmasters can prevent Google from monitoring web pages by using the features that block Googlebot from crawling or caching web pages. This suggests that Google Reader's page monitoring uses data from Google's search index and the changes may not be detected quickly if the web page is not popular or it doesn't change often.

Since I rarely visit Google's homepage, generating a feed for google.com or for other international Google homepages is a great way to track all the doodles and the promotional messages.


For now, Page2RSS offers more features (posts have better titles, you can view a cached version of the page), but Google Reader is more reliable. For example, Page2RSS doesn't show the latest changes for google.com.

Tip: to find the URL of the feed generated by Google, click on "show details" and you'll find a URL like:

http://www.google.com/notificationservice/webchanges/webfeeds/11009120664050806769