To me it's not a given since AFAICT Apple software doesn't sync with Google Calendar over CalDav by default. Particularly on iOS you have to go out of your way to enable it—viz. you have to select 'Exchange account' instead of 'Google account'.
In any case, if they're committed to preserving this feature then why are they implementing screening?
Seems unlikely they'll drop it given their approach to iOS so far has been to infiltrate the ecosystem with their own Google apps, though never say never I suppose.
As for why they're pushing people towards their own Calendar API, presumably so they can add/promote new features specific to Calendar which aren't present in CalDav. They can get more usage of Calendar-specific APIS/Features by pushing devs towards their own version, instead of letting them default to the CalDav API because that's what they're familiar with.
The responses gathered from API request form also act as a feedback mechanism for their own Calendar API, which they can use to fix any deficiencies.
>Seems unlikely they'll drop it given their approach to iOS so far has been to infiltrate the ecosystem with their own Google apps
Yes, and syncing Calendar data with Apple's calendar App is not this strategy.
Releasing a standalone "Calendar" app for iOS to keep it accessible, controlled, and branded on iOS devices after it stops working and Apple doesn't bother to request whitelisting but promotes iCloud instead, is.
Not sure why Google would block themselves server-side if they themselves wanted the current iOS 6 account-sync set up to continue. Apple doesn't really factor into it at all.
Google breaking off into their own Calendar app is a possibility, but its not clear cut that they would do this since there's a definite "stickiness" to having the Calendar sync option pre-checked as soon as the user adds his/her GMail account.
Look, the announcement was clear that they are sunsetting the CalDAV API and if someone wants to continue using it, they need to make a request to Google, and explain why. (Via the form you linked to previously)
One would hope Google has enough sense just to keep this working with no hiccups for Apple, but it also is not clear cut that they will from the information we've been given. (Or that Apple gives a shit either way)
It's not like they are seeking feedback on how to improve CalDAV, they're moving away from it.
Actually, if you'll read the ZNet article that post is based on you'll notice that users who didn't connect their Windows Phone calendars to their Google accounts before February are still screwed!
I want to connect my Google account after January 30, 2013
Here's what you need to know:
Unfortunately, with Google changing the way it supports EAS,
your Google calendar can’t sync with the Calendar app.
Read the article again. Windows 8/RT isn't the same as Windows Phone (which Google confirmed in the article has been whitelisted). The source of that is the Windows team deciding not to add CardDav/CalDav support to the Metro-style Mail and Calendar apps, so you won't be able to use CardDav/CalDav from any other provider either.
So what about the decision to drop ActiveSync support for anything after Windows 7/Office 2010? If you buy a new windows machine and are a paying apps customer, you are pretty much screwed. Dropping CalDAV doesn't affect this, but it is icing on the cake since it's hardly a guarantee that Apple is going to request whitelisting to make sure it works. (They have iCloud after all & not seeking interoperability will push iCal users who weren't using it for this, toward it.)
CalDAV is the standard and it's pretty clear that Google is backing away from that along with ActiveSync for enterprises and therefore silo-ing Calendar.
Also why would Apple have to request addition to the Google Calendar CalDav whitelist on iOS? Google could just whitelist it themselves since its them who decides whether or not it continues server-side.
>Where are you getting that they dropped Google Apps Activesync support for Outlook 2013?
From the original December announcement that's since been extended, amended, and clarified. And from the fact that at present, it still doesn't work.
Both of your links are relatively new developments. I'm glad to see that this is happening.
I've already spoken to why Apple would have to request whitelisting. The way Google announced plans to phase out CalDAV indicated such. Not for Apple expressly, but for anyone using CalDAV.
I hope you're right and I'm wrong, but none of this seems like simple "housekeeping" It seems like "platforming" or "silo-ing" Calendar in an analogous way to what Twitter did/is doing with its API and 3rd party clients. I readily admit this makes little sense for Calendar, but phasing out support for the most popular sync protocols used to by the 2 most popular software platforms -one of which is the open standard, then allowing them by exception only, is suspect.
Even Windows Phone 8 has that confirmed: http://www.engadget.com/2013/03/15/google-caldav-support-sti...