3 ms·

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 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?

Shooti 14y ago
CalDav is what the iOS Add Account option for Google uses to sync: http://support.google.com/calendar/bin/answer.py?hl=en&answer=151674 http://support.google.com/calendar/bin/answer.py?hl=en&a... 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.
- DigitalTurk 14y ago
  I see. Thanks for sharing. What a confusing mess!
- spinchange 14y ago
  >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.
  - Shooti 14y ago
    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.
    - spinchange 14y ago
      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.

Shooti 14y ago

CalDav is what the iOS Add Account option for Google uses to sync: http://support.google.com/calendar/bin/answer.py?hl=en&answer=151674 http://support.google.com/calendar/bin/answer.py?hl=en&a... 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.

DigitalTurk 14y ago
I see. Thanks for sharing. What a confusing mess!
spinchange 14y ago
>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.
- Shooti 14y ago
  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.
  - spinchange 14y ago
    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.