Hacker News Reader

> If you throw out all the 'tit-for-tat' assumptions, it really makes sense. Google has an API for nearly everything. I could easily see this as a standardization approach.

Except caldav is just a protocol. It's not an API. Google could have made an API that supports the caldav protocol, but chose not to.

This also effects me a lot, personally, because I have a Kindle Fire and an iPhone, and I use my Google calendar to sync up everything between the two.

View on HN

So then the Google calander API has always been used, but the data is delivered in CalDev format?

This move would then represent Google refusing to accept that format?

I didn't read things that way.

It makes good business sense - look at Maps API. You can get X number of free calls, but if you go over a certain limit you need to pay (That limit is pretty high if I recall)

So now fast forward to Microsoft and Others incorporating that API into their products - am I understanding correctly Google could charge for API calls similarly?

Reply on news.ycombinator.com