Home

Google To Close Reader In Product Purge

Comments | Thomas Claburn, InformationWeek | March 14, 2013 03:00 PM


Google on Wednesday returned to culling products, features and services from its portfolio, announcing plans to discontinue eight offerings, including Google Reader.

The company's campaign to focus on a few popular products rather than everything its engineers can imagine -- euphemistically referred to as "spring cleaning" and described by CEO Larry Page as an effort to put "more wood behind fewer arrows" -- has led to the termination of over 70 products, features and services since September 2011.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

As detailed in a blog post, Google plans to close, deprecate, stop supporting or otherwise limit the following products: GUI Builder, CalDAV API, Google Building Maker, Google Cloud Connect, Google Voice App for Blackberry, Search API for Shopping and Snapseed Desktop for Macintosh and Windows.

But it's the company's plan to shut down Google Reader in July 2013 that has upset a large number of Internet users. Google Reader remains a popular way for people to aggregate RSS feeds from their favorite websites in one place. Though Google insists "usage of Google Reader has declined," as Google engineer Alan Green put it in a blog post, the company has not put this alleged decline into context.

[ Sick of ads? You'll get no respite at Google Play. Read Google Play Bans Ad Blocking. ]

Buzzfeed, a popular news aggregator, claims that however much Reader has declined, it still refers more traffic than Google+.

Unhappy users of Reader are voicing their resentment and trying to reverse Google's decision. A thread on Storify has collected tweets of discontent. A petition posted to Change.org asks Google to reconsider. It has been endorsed by Google Reader fans over 64,000 times in less than 24 hours.

Google remains unmoved. A company spokeswoman said in an email that Google has explained its rationale for closing Reader in its blog posts -- dwindling user interest and the company's desire to focus -- and that the company doesn't have anything more to say on the subject at this time.

This is far from the first time that unhappy people have taken to venting via social media. Previous Google product closures, like the announced plan to discontinue iGoogle, prompted similar objections and sent large numbers of users in search of alternative services.

NetVibes, which took in users abandoning iGoogle, has issued an invitation to Reader users. The solicitation appears to have been too effective: NetVibes posted a notice to its users this morning stating, "If you're experiencing slowdowns or feed latency, please bear with us as we work hard to handle a huge amount of new users."

Newsblur, another service mentioned by Internet users looking for a Reader alternative, has been suffering slowdowns due to the sudden flood of interest. The service temporarily suspended free account creation in order to restore operations.

Google's decision to put Reader out to pasture suggests that the company didn't see a viable revenue stream in its RSS feed service. However, that doesn't mean RSS is a doomed technology. Developer Marco Arment argues that the closure of Reader will bring much-needed innovation back to RSS app development.

Attend Interop Las Vegas May 6-10 and learn the emerging trends in information risk management and security. Use Priority Code MPIWK by March 22 to save an additional $200 off the early bird discount on All Access and Conference Passes. Join us in Las Vegas for access to 125+ workshops and conference classes, 300+ exhibiting companies, and the latest technology. Register today!



Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

COMMENTS

Tune In to BYTE
Facebook Twitter LinkedIn Newsletter RSS
Whitepapers
whitepaper
In this paper you will learn the five trends shaping the future of enterprise mobility. Learn how the rise of social media as a business application, the lurring between work and home, the emergence of new mobile devices, the demand for tech savvy employees and changing expectations of corporate IT will fundamentally change the workplace.
whitepaper
In a survey of more than 1,700 information workers (iWorkers) in North America, notebooks, desktops, and smartphones were found to be “must-have” devices, while tablets, slates, and netbooks were relegated to “nice-to-have” status, according to a commissioned study conducted by Forrester Consulting on behalf of Dell and Intel.
Sponsored by: Dell
Upcoming Events