Something that didn’t get quite as much attention as Reader was Google’s dropping of CalDAV support:
CalDAV API will become available for whitelisted developers, and will be shut down for other developers on September 16, 2013. Most developers’ use cases are handled well by Google Calendar API, which we recommend using instead. If you’re a developer and the Calendar API won’t work for you, please fill out this form to tell us about your use case and request access to whitelisted-only CalDAV API.
I suspect major platforms and apps such as iOS will be whitelisted automatically until iOS makes full use of Google Calendar’s API (I’m under the impression that the setup in iOS for Google just uses CalDAV as described on the Google Calendar iOS help page).
Unless your app makes it onto the whitelist then accessing Google Calendar will no longer work without switching to Google Calendar’s API. For OS X Leopard users, that could be a big deal. It’s been seven years since Apple introduced Intel and five years since the launch of Snow Leopard so if you’re still running Leopard but use Google Calendar, either start using the web interface or look to move onto a more recent Mac.
The strange thing is, Google enabled CardDAV for Google Contacts not that long ago, back in September 2012. It doesn’t seem to make much sense that they’d drop one particular extension of WebDAV after introduce another. When CardDAV was implemented by Google, it was thought they were moving towards more open technologies for contacts and calendars. My only assumption is Google, whilst continuing to prune what they make available, are planning features that might not necessarily be supported by CalDAV.
I wonder how long it’ll be before POP/IMAP support in Gmail is dropped?