Seems practically a given that Apple iCal and iOS will be whitelisted by Google as clients.
Even Windows Phone 8 has that confirmed: http://www.engadget.com/2013/03/15/google-caldav-support-sti...
Even Windows Phone 8 has that confirmed: http://www.engadget.com/2013/03/15/google-caldav-support-sti...
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.
Thanks for sharing. What a confusing mess!
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.
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.
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.
See also http://windows.microsoft.com/en-US//windows-8/use-google-win... :
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.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.
A search brought up the main support page which says its upcoming (Under "OS and Microsoft Outlook® requirements"): http://support.google.com/a/bin/answer.py?hl=en-uk&hlrm=...
It also brought up a Google groups thread where a Google representative posted last month saying they're working on it: http://productforums.google.com/forum/#!topic/apps/rUd8phVXs...
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.
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.