<story><title>Google Drive Realtime API</title><url>https://developers.google.com/drive/realtime/</url></story><parent_chain><item><author>polskibus</author><text>I&apos;m still irritated with Google Reader story. How long is this one going to be around, year, two? I think Google should start pledging a number of years they will support a service, why should the developer be taking most of the risk?</text></item></parent_chain><comment><author>notatoad</author><text>Don&apos;t build a business or product that relies on a proprietary API with no service agreement.  APIs with no service agreement are okay if they&apos;re well-documented and have multiple providers, proprietary APIs are fine if they have a service agreement.  Something like this should not be used as the base for your product, it should only be used as a means to provide an extra feature to an existing service.  This is allows you to integrate your real-time web application with drive, it&apos;s not a foundation to build your real-time service on top of.&lt;p&gt;Just because google shut down reader doesn&apos;t mean that this applies to their APIs more than any other company&apos;s.  If you build something that relies on an API that can disappear at any time, you have nobody to blame but yourself.</text></comment>
<story><title>Google Drive Realtime API</title><url>https://developers.google.com/drive/realtime/</url></story><parent_chain><item><author>polskibus</author><text>I&apos;m still irritated with Google Reader story. How long is this one going to be around, year, two? I think Google should start pledging a number of years they will support a service, why should the developer be taking most of the risk?</text></item></parent_chain><comment><author>ewolf</author><text>There never was any official Google Reader API. Every developer was aware of the risk he was taking when using an unoffical and undocumented API.</text></comment>