In that case, I guess that we can praise Apple for meeting the "crazy high bar" for "supporting open standards" since Apple decided to include support for the most widely used open protocol for calendar and contacts in their mobile OS.
In that case, I guess that we can praise Apple for meeting the "crazy high bar" for "supporting open standards" since Apple decided to include support for the most widely used open protocol for calendar and contacts in their mobile OS.
If so it is a bit of a weird thing for Android not supporting those protocols to be considered a 'crazy high bar' of effort. If the other smartphone OS's support them, it is somewhat curious that Google doesn't as well. Even when they support it server side. Strikes me a bit too much like a Hotel California situation.
I'm not sure why posters ITT are acting as if I am making demands to Google. In my original post I simply stated that "it would be nice" to see native CalDAV/CardDAV support in Android. But apparently making suggestions for a better product by providing the same support for open standards that other OSes provide is "a childish perspective" according to a Google employee [2]. I guess we need to keep in mind that a client and a server are barely even related [2]. TIL.
[1] http://www.engadget.com/2013/05/14/windows-phone-8-summer-up...
For example, Samsung, Asus and Sony do exactly that. They provide their own sync adapters. Maybe that's more important to them (and their customers) than generic CalDAV/CardDAV.
Trying to build CalDAV and WebDAV into the Android OS wouldn't work, because they would be dependent upon those applications, which would then make them essential OS applications.
It does not matter, as neither AOSP nor vendor-specific Contacts or Calendar applications contain any protocol code. These frontends use contact and calendar specific content providers, which in turn provide plugin based API for sync adapters. Google's own sync adapter is such plugin, as well as Facebook's or even Microsoft's (for Skype contacts).
It is true, that there are no CalDAV/CardDAV sync adapters on the devices. However, because not everyone is interested in one, it is perfectly fine to install them from Play Store for those interested.
I do find the dichotomy of supporting "open" protocols to their service, but not from their operating system a bit odd. Though in that respect Apple isn't much different regarding imessage/facetime/etc...
I guess I would rather have my device/os support open standards over the service I might use them upon.
For an OS, it makes more sense to err on the side of supporting fewer protocols by default and allowing users to clients to add the ones they need than bloating it up with all possible protocols you ever might want to connect to on any server, anywhere.
I do realize that all of these run in userspace and technically are not a part of the Operating System but they are provided with the distribution/purchase.